I think I will end up just writing my own model for this (a la Anthony's suggestion), but the problem remains that "model" as it relates to web2py presumes SQL, and that fact limits design. While it would be possible to write an XMLRPC adapter to the DAL, that is sort of like jamming a square piece into a triangle hole - more than not you'll probably end up wishing you just used the direct database connection! I think the long term solution to this problem is to decouple the data models from database access.
Cheers, Matt On Mon, Sep 26, 2011 at 2:05 PM, Ross Peoples <[email protected]> wrote: > Please forgive me if this post shows up a bunch of different times, but I'm > having trouble with Google Groups not posting my replies, even though it > says it did. So for the fourth time: > We could add an XMLRPC adapter to the DAL that instead of making SQL calls, > could build an XML version of the query that could be passed on to another > web2py app via xmlrpc. That app could then return the results as XML, which > is then converted back to Row objects and returned to the application, > making XMLRPC remote database access completely transparent and make things > like SQLFORM.grid work. > The only problem I see (aside from there being a lot of work to do) would be > security. We would have to make web2py apps acts as a db service, like it > does with CAS, and restrict who can access the XMLRPC-DB service. But this > would be VERY cool and extremely helpful in building scalable (multi-tier) > apps. > I would be interested in helping to write code to make this happen.
