It started with IMs from Zania Turner at Starfleet Command, SL Quadrant, who’d bought a CogBoard for handling events at one of the premier RP sims in Second Life. I helped her get the board up and running; pretty soon I get an IM from a colleague of hers, who handles Starfleet training events! Wow! They run close to 250 events over a two-week period! The server and board have never been so heavily tested! This sent Ali to the science officer station a few times, required us both to be added as subscribers to the Google calendar handling the Starfleet training events, and pushed us to upgrade the whole product! The big change is that you can now add ONEDAY=TRUE to the settings notecard and have it display the current day’s schedule of events. For the Starfleet board, that’s equivalent to just about anybody else’s two-week interval! The upgrade also made it possible for us to automate sending out future upgrades.
This was all fine and good, but when our new contact at Starfleet ran it, the events for a day one week in advance of the current day would display. WTF? Well, here’s how Ali explained this new glitch:
“Basically, when I ask for all events from a calendar within a certain range, Google returns them to me in reverse order of start date (I have no idea why) so I sort them correctly, translate them into something SL friendly, and send them off to the requesting object (the board’s server, a kiosk, whatever).
“Now a year or more ago when I was writing this, I had to put a limit on the number of events I retrieved from Google and I chose 100. What this meant was that for any one calendar I would get 100 events for the range I specified. This is fine for HUDs (which only retrieve a day’s events at a time), but as you will see in a moment, not great for people with giant calendars.
“Because I was only getting 100 events, and they were in reverse order, Google was only returning me the last 100 events on a calendar in that range. Since kiosks/squares/boards ask for 2 weeks of events at a time they were getting the events at the tail end of that 2-week period. I would sort them, translate, and send them back to SL. It seems the Starfleet calendar has about 250 (maybe more) events in that time frame. So I was getting the last 100, which after sorting started the 24th or so and was sending those to SL. [The day of reference, of course, was the 17th!]
“I’ve upped this number to 500, we’ll see if we need to up it sometime in the future, but the Starfleet calendar should be working now (or, in an hour when the board and server reset themselves). ”
That seemed to do the trick except even then, a few later-in-the-day events got truncated! (This is a problem we expect no one else to experience!) Good grief! I was ready to call in the Klingons to do a preemptive on Starfleet! It turns out that SL has a limitation on the number of characters you can receive from such a feed, so Ali once again had to make some adjustments to refine the amount of information that was going to SL from Google. Problem solved!
We are very glad to have done our part to keep the SL Quadrant safe!
Comments