On Oct 4, 2008, at 11:22 AM, Ed Leafe wrote:

> Of course, this requires a web server in order to work. I'm almost

> ready to post the one I've developed. It's a Pylons app; I chose

> Pylons since that's the framework with which I'm most familar. There

> is absolutely no reason why the this wouldn't work equally well with

> any other Python web server, as the only thing it needs to be able to

> do is route URLs to the correct methods in the controller, and return

> standard response objects and codes.

I've just posted the server side of things. It took me a while

because there are all sorts of unicode encoding/decoding issues

involved in passing non-ASCII data back and forth over the http

connection. It still needs some work, but I'm able to work with it.

If you're familiar with Pylons, when you create an app named 'foo',

the directory structure is an outer 'foo' directory, containing

distutils-type stuff and an inner 'foo' directory that contains your

app. I named my app 'daboserver', and since the outer directory is

boilerplate, I've only committed the inner 'daboserver' directory.

In that directory is an 'appSource' directory that contains a folder

for each web app you are hosting. I created a simple datanav app based

on the 'orders' table in the public dabodev.com database. I chose that

table because it contains non-ASCII values, making it easier to find

encoding issues.

There is also a 'controllers' directory; in an MVC framework, the

controller is analogous to our bizobj, so that's where you put the

RemoteBizobj files. The file 'bizservers.py' is the main controller,

and it is what you would customize for your bizobj classes. It also

contains the file updating functions, which should properly be in

their own controller, but hey, this is just a start.

-- Ed Leafe