T.J. Jankun-Kelly wrote:
> I have a question regarding sessions and PickleRPC. I have a
> site that
> has severl normal pages (derived from Page) and a few from PickleRPC.
> The PickleRPC does some work that the Page logic would not seem
> appropriate for. I planned on using sessions to send
> information between
> the two groups. However, the sessions created by the Pages are not
> treated the same as those created by a PickleRPC interaction
> (i.e., they
> have different identifiers). Is this by design or is this a bug?
I don't think sessions work with PickleRPC at all. Session IDs are normally
transferred using cookies, but I'm pretty sure that the PickleRPC client
doesn't save any cookie state. Correct me if I'm wrong...
That would be a nice feature to add to PickleRPC though. It doesn't seem
all that hard to do.
Actually, for the purposes of PickleRPC we could transfer the session ID any
way we want, since we have complete control over both client and server. We
(Another nice feature to add would be some sort of authentication. Right
now you can write authentication code that is based on the contents of the
pickled message, but it would be better if we could authenticate first, and
only AFTER authenticating the user would we unpickle the message.)