On Tue, Feb 17, 2009 at 10:57:20AM -0800, Marek Szuba wrote: -> On Mon, 2 Feb 2009 19:59:23 -0800 -> "C. Titus Brown" <[email protected]> wrote: -> -> > If it's important to provide a non-HTTPS connection, we can run two -> > servers at once, in different threads. This does mean that each -> > served function needs to synchronize data access appropriately -- -> > which is going to be an issue in *any* threaded server. -> -> I thought about this and it seems we need to design a synchronisation -> mechanism before we even begin to consider adding write capabilities to -> the XML-RPC server. Any thoughts on the subject, Titus? Also, do you -> think a server should limit write operations to local/SQL storage, or -> should it be able to manipulate data it pulls from other servers as -> well?
How about just using a simple write lock around any sections that modify pygr.Data, or (even simpler) around any XML-RPC-exposed functions that modify pygr.Data? I don't have a sense of how hard it would be to be able to manipulate remote data -- do you mean download & then manipulate? -- but I suspect it would be useful ;) -> > XML-RPC as a protocol doesn't support authentication AFAIK, and it's -> > based on HTTP, which is stateless, so you can't simply authenticate -> > the connection. I dealt with this in one of my projects by simply -> > serving an auth cookie with any privileged function. -> -> That's the way this is normally done, I believe. -> By the way, would you be able to transplant your auth code from your -> other project into Pygr? Unfortunately, no -- I was using the Quixote session2 module to generate the auth key, and that's not really portable between Web servers. The client side stuff was trivial: retrieve key, store key, pass key back as first argument of any function... cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
