Webware for Python

I chose for my current webware app to store pickled objects to 
PostgreSQL which works fast and so far flawlessly.    I opted to use 
the text option of pickling so I didn't have to store binary  data into 
the databse; I just created a TEXT field and stored the data thee.   
You lose the ability to query the object data but for my purposes that 
wasn't necessary.

Mike
On Thursday, January 30, 2003, at 10:27  AM, Bill Bumgarner wrote:

> My next step is to figure out object persistency.   My mind is wrapped 
> around relational based persistency simply because that has been what 
> I have been doing for a long time (and because I already have a 
> relational database-- in FrontBase-- full of data in a particular 
> schema that I wish to interact with from WebWare).

I have had 1 Meg session objects w/o any real problems. (<50 concurrent 
users though)

Also, webware is just a python app, so you can create lists and caches 
at the module level and use that.  (If you do not need the objedts 
between app restartes then its pretty easy.

-Aaron


Michael Engelhart wrote:

> I chose for my current webware app to store pickled objects to 
> PostgreSQL which works fast and so far flawlessly.    I opted to use 
> the text option of pickling so I didn't have to store binary  data 
> into the databse; I just created a TEXT field and stored the data 
> thee.   You lose the ability to query the object data but for my 
> purposes that wasn't necessary.
>
> Mike
> On Thursday, January 30, 2003, at 10:27  AM, Bill Bumgarner wrote:
>
>> My next step is to figure out object persistency.   My mind is 
>> wrapped around relational based persistency simply because that has 
>> been what I have been doing for a long time (and because I already 
>> have a relational database-- in FrontBase-- full of data in a 
>> particular schema that I wish to interact with from WebWare).
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Webware-discuss mailing list
> Webware-discuss@...
> https://lists.sourceforge.net/lists/listinfo/webware-discuss

Yeah, I wasn't storing sessions though.  My app builds up an object 
that the user can later retrieve and edit and then store back into the 
database.   There is a also a daemon application that retrieves the 
objects and acts upon them separate from the webware application.

Mike
On Thursday, January 30, 2003, at 11:30  AM, Aaron Held wrote:

> I have had 1 Meg session objects w/o any real problems. (<50 
> concurrent users though)
>
> Also, webware is just a python app, so you can create lists and caches 
> at the module level and use that.  (If you do not need the objedts 
> between app restartes then its pretty easy.
>
> -Aaron

On Thu, Jan 30, 2003 at 10:27:26AM -0500, Bill Bumgarner wrote:
> Hello,
> 
> I am a long time WebObjects / Java / Python / Cocoa / NeXT / Lisp / etc 
> developer that has been building [mostly WebObjects] based internet 
> related apps/sites for quite a while now.

.. 

> My next step is to figure out object persistency.   My mind is wrapped 
> around relational based persistency simply because that has been what I 
> have been doing for a long time (and because I already have a 
> relational database-- in FrontBase-- full of data in a particular 
> schema that I wish to interact with from WebWare).


First I need to apologize for this long time answer. 

I've been working a long time with a python <=> rdbm bridge in 
my previous job ( unemployement now :( ). For those which are 
interested, the code just went to GPL (Thanks to the author 
Sebastien Bigaret). 

As I read in your mail, you seem to know EOF, so I think you 
should give it a try, since the "modeling" (it's the name) have
same API (ObjectStore,Qualifier, .. ) 

Despite the fact, it has been develop for zope, it works great
without it. We use it to build a bookstore app with gtk.

I hope to find some time soon to make a short introduction, 
as this every one can make its own opinion. 

home page http://modeling.sf.net 

Bye bye ..