ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
3.0 SDK not worth it... (Sdk)
3.0 SDK not worth it... // Sdkandon13Oct 24, 2000, 12:25pm
I've been using the 3.0 SDK in my primary BOT project since it was released,
and the only thing I have to say is... It's not worth it. Sure the ability to telport someone else sounds cool, but the features the 3.0 SDK has disabled outweigh the good... Mainly what I'm referring to is the ambiguity of the Universe Connection errors now. Where as in the past it would return a useful non-zero error code, now all it returns is 439 (Unable to connect). Very hard to explain to my users that when it says this it could mean practically anything. Also, somehow the World List Callback or perhaps the way aw_int and aw_strings are stored in the memory has changed, because the World List is no longer thread safe. I have to run it in a thread in my case, because the method I use to store the World Info is rather slow on some machines, but on others it's very fast... I probably ought to re-evaluate the situation, but in the mean time I'm going back to Build 15 which will alieviate some of my headaches. So, in essence... For the reasons stated above, I am concluding that the AW 3.0 SDK isn't worth re-compiling your programs with, unless you can find a practical use for Avatar Teleportation that outweighs the loss of the two abovementioned statements. For some of you, the AW 3.0 SDK may be fine and dandy and that's great, but in my case it's not worth the increased executable and DLL size after compilation. Best Regards, Andon M. Coleman Senior Programmer, R&D Nothing, Inc http://www.nothing-inc.com/ P.S. If you figure out a method to fix the two problems mentioned above in the 3.0 SDK feel free to give me a jingle at : CodeMaster at Nothing-Inc.com xelagOct 24, 2000, 7:50pm
Hi andon13,
I have not noticed any difference at all in performance between build 15 and 17. On the contrary, besides adding features, Roland fixed a few bugs: 1. teleporting the bot to a world in a universe with a name also used and visited by the bot in the last 30 minutes in any of the universes it has been would cause havoc (world ip:port data remained cached and inmutable so bot could not go into that world and error messaging was wrong and confusing). Fixed. 2. a world error (like for instance ejection or world-wfs) would cause the bot, if teleported by the owner somewhere else, to land at the same spot as it was in the previous world, to the greatest joy of the abominable sadist Custom Aids bot. Fixed I think (I had a workaround, and never removed it, so I haven't tested it) 3. a new error introduced in build 16 was repaired in 17: world ejection database was not being updated properly by the bot. Fixed. The World list feature never changed, in my experience. Universe connection error handeling has always been extremely lousy, so that is not a new 'feature'. I do not see how it ever could go worse from build 15 to 17 ! And until the winsock connection is made non-blocking (as it is in the browser), or the sdk is made thread safe and client connections are threaded, we will never have full control on how our users experience our bots. XelaG Antique and Fossilized Programmer AAGdC (y a mucha honra) [View Quote] |