Hi, On May 29, 2007, at 1:17 PM, Norman Rasmussen wrote:
> On 5/29/07, Pedro Melo <[EMAIL PROTECTED]> wrote: > This is an interesting issue, the backends. In the recent months, > I've taken a different approach: support a single backend - HTTP- > based REST webservices. > > They are easily plugged in into the async nature of transports, and > they give you an abstraction layer that can make your transports > accept any kind of backend, SQL or not. > > errr, but then you need a full http server, etc. I was actually > thinking of writing a wrapper layer for the backends that _looks_ > (and behaves) like python's normal shelved objects. This means > none of the transport's code would have to change to support > different backends, you'd just load up the initial db file > differently. Yeah, :) but then again, big users of py* alrady have loads of HTTP servers, complex DBs behind, and know how to tune them. Also lot's of solutions for HTTP load balancing, caching and other stuff. Its not for everybody probably, but it is, at least for us, an interesting concept. Best regards, -- HIId: Pedro Melo SMTP: [EMAIL PROTECTED] XMPP: [EMAIL PROTECTED] _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
