Prepping an item for possible updates

Awesome.

If I manage to write an inworld server/client pair that *DOESN'T* suck, I'll contribute it to the project.

EDIT: However, I may hold off until we have HTTP IN on the live grid, so doubly don't hold your breath.

Surprisingly, this application may not be a lot better off with HTTP-In. The reason is that with in-world servers polling the web server, you can easily create a distributed, redundant set of in-world server objects. If you did it the other way, it might be difficult to produce metrics that would allow the web server to know which in-world server to utilize at any given time. If you really intend to always have just one in-world server processing requests then I suppose it would be fine, but I like the kind of stability the polling option can produce myself.

Ah, I would have thought it could go both ways, keeping its status updated with out requests, using in requests for any queries from the server to send something, that way you wouldn't need to go through the effort of storing a request to have it sent in reply to the next ping.

Then again I don't know any real languages so I'm probably talking out of my rear end.

You're quite right, actually. It just doesn't lend itself well to having more than one in-world giver object. If you will always have only one, it works fine.

I see, fair enough. I noticed SourceForge has put it up now... When the package is posted I'll try to get the inworld stuff going for it.

Someone else will have to do the interface stuff, unless you plan to do it later.

Okay. SVN and a downloadable ZIP archive are available on SourceForge.

http://openslprodupd.sourceforge.net/

I've created a new thread for the discussion of the Open SL Product Update Server application.

/54/b2/308491/1.html