Others may have more specific advice regarding xmlrpc setups, but in general, you can put whatever you want in your model files, so if you are duplicating code related to processing your xmlrpc calls, you could move it to model files (or to modules and import them). You can also use SQLFORM.factory to take advantage of web2py's forms functionality when there's no database involved -- see http://web2py.com/book/default/chapter/07#SQLFORM.factory. Anthony
On Monday, September 26, 2011 11:47:30 AM UTC-4, Matt wrote: > Greetings, > Has anyone successfully used web2py to develop an app that does not > use a database backend, but instead operates on a system using xmlrpc > calls? > > Our current approach was to simply ignore web2py's models completely, > putting all the functionality in the controllers and views. The > problem with this approach is you begin to run into massive > duplication of information that would usually be stored in models. I > am interested specifically in two things: > - encapsulate schema information to (among other things) provide > proper data validation > - ease of form generation > > Implementing a new fake database backend seems to be overkill here > because we only need such a small subset of functionality offered by > the DAL. Any suggestions would be welcome! > > Thank you, > Matt
