Re: Where does the data go?

Jacob Smullyan wrote:
> On Fri, Sep 09, 2005 at 07:34:45PM -0700, Gregory Brauer wrote:
> (The raw
> input can be found in CONNECTION._stdin.)  
> 
> My guess is that you just need to set the content-type appropriately,
> and you'll be good to go.

Excellent!  CONNECTION._stdin was what I was looking for.

The data I am sending has no established content type (that I
know of) but it does have a decoder written, so I just need to get
at the data in order to pass it to the decoding function.

For the curious I am experimenting with passing data objects
directly between Javascript on the client and Python on the
server (via Skunkweb) using JSON.
http://www.crockford.com/JSON/index.html

It works now.

One could potentially use this with PyDO, mapping a list of fetched
PyDO objects to standard Python dictionaries on the server and passing
that list of dictionaries (asynchronously via XMLHTTPRequest) to the
client where they will automatically appear as a standard Javascript
indexed array of associative arrays.  They could then be modified by
Javascript embedded in a web page and passed directly back to the
server (asynchronously, again) where they reappear as a Python list
of dictionaries again which can be used to update the database.  It
is the closest thing I can think of to having PyDO embeded directly
in your browser.

Greg



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf