On Feb 2, 10:59 pm, "C. Titus Brown" <[email protected]> wrote:
> I think this can be addressed by making it multithreaded with the > SocketServer.ThreadingMixIn, yes? Although threading adds in a big heap > o' problems... pygr.Data is probably not threadsafe, right, Chris? I think for read access it could work as is. Safely writing to the resource however would need more work. I can imagine though this being data that is mostly read only. So one can just stop the XMLRPC server while writing to the resources. > 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. Do you mean needing a 'password' type argument for each XMLRPC function, and only returning data if the password matches? That's how I read this above. Istvan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
