On Mon, Nov 12, 2007 at 11:55:10AM +0000, Julian Bond wrote: > > Just looking at the sample container code. "Due to browser security > restrictions, your gadget definition file and system state file must be > on the same server as the container." > > How is the architecture going to change to get over this? Clearly in the > Orkut sandbox this isn't the case and the definition file can be > anywhere on the web. > > As a prospective container developer, I'm struggling at the moment to > try and work out what I can usefully work on now. It seems like each > part of the game is partially specced, implemented, or supported.
The in-memory container is just that, in-memory. That means no server side processing is required (nor allowed for). This means you can load the data from the filesystem or any old web server. You can also use it as a basis to do further development, as we've done at hi5, or you can use it to test your gadget without using any server backends... Or you can use it to unit test specific combinations of owner/viewer/state. -- Paul Lindner hi5 Architect [EMAIL PROTECTED]
pgphmsdu39JrN.pgp
Description: PGP signature
