OpenID Libraries should be stateless

[Ryan Ernst]

I understand it is the same amount of work, and I'm happy to do it, but I
don't want to do it (assuming certain internals of the library) and then
have to check with each new release of the library that my code hasn't been
broken.  I have no problem storing the state into a dictionary as it is now,
but I would like to pass the values of that map as get parameters, signed.
Once I have more than one application server, I can't do that (the object
references won't make sense anymore).

Instead of making a different class, couldn't it just be a setting  when the
class is intialized (serialize_on_save)?

Thanks
Ryan

On Feb 5, 2008 11:43 AM, Kevin Turner <kevin at janrain.com> wrote:

> oops, forgot one relevant detail here, which is
>
> > What Josh was suggesting is that this work be done in an alternate
> > implementation of openid.consumer.consumer.Consumer,
>
> that makes uses of openid.consumer.consumer.GenericConsumer, which is
> where all the OpenID logic really lives, independent of any session
> mechanism.
>
>
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.openidenabled.com
> http://lists.openidenabled.com/mailman/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openidenabled.com/pipermail/dev/attachments/20080205/e7160cd5/attachment.html