On Jan 30, 2008 5:40 AM, Reinoud Elhorst <[EMAIL PROTECTED]> wrote: > On 1/30/08, Brian Eaton <[EMAIL PROTECTED]> wrote: > > > > - user logs in to the container > > - container uses the GadgetServer to render the gadget in 'Container' > > mode (which doesn't do much at the moment) > > - container uses GadgetSigner (which I'm renaming to > > GadgetTokenSigner) to create the security token for the gadget > > I guess this is only useful if the container site is in java as well. Our > site is in PHP, so I guess I need to convert the GadgetSigner to PHP > (probably make some people on the PHP branch happy by conrtributing it back > :) ). Am I correct in seeing that there is no actual signing (so no actual > security) in there at the moment?
That's right. At some point we'll put actual authentication in that code, but for now ironing out any kinks in the high level design is more important. Would you mind outlining your architecture for me? Will you be using the java gadget server with a PHP container? Or are both the gadget server and the container going to be PHP based? Cheers, Brian
