Webware for Python

On Wed, 2003-01-29 at 10:16, Bill Eldridge wrote:
> What relationship, if any, does this have to MiddleKit?

It has similar functionality to MiddleKit, and is meant to aid in the
same situations, but does so in a different way.  Neither is actually
related to WebKit (and hence most of Webware), but of course they are
useful for web/database applications.

-- 
Ian Bicking           Colorstudy Web Development
ianb@...   http://www.colorstudy.com
PGP: gpg --keyserver pgp.mit.edu --recv-keys 0x9B9E28B7
4869 N Talman Ave, Chicago, IL 60625 / (773) 275-7241

On Wed, 2003-01-29 at 11:56, Ian Bicking wrote:
> On Wed, 2003-01-29 at 10:16, Bill Eldridge wrote:
> > What relationship, if any, does this have to MiddleKit?
> 
> It has similar functionality to MiddleKit, and is meant to aid in the
> same situations, but does so in a different way.  Neither is actually
> related to WebKit (and hence most of Webware), but of course they are
> useful for web/database applications.

Sounds a lot like PyDO from the skunkweb folks.

-- 
Karl Putland <karl@...>

I don't know a good tutorial, but the session class is here:
http://webware.sourceforge.net/Webware-0.8b1/WebKit/Docs/Source/Summaries/Session.py.html
and you can access a session from your servlet via:
self.session()

ie:
#test for a session var:
	if (self.session().hasValue('sortOn')):
# pull in a session var (any python object)	
	sortOn=self.session().value('sortOn')
#pull in a seeson var w/ a default of '0'
	sortOn=self.session().value('sortOn',0)
#set a value
	username='aaron'
	seld.session().setValue('name',username)
#delete a value
	self.session().delValue('name')
#get sessionID
	SID = self.session().identifier()

jose@... wrote:
> Hi all,
> 
> Could someone please point me to a good tutorial on how to use sessions.  I
> have looked at the example docs and the only one that uses session is
> really pretty simple.  Specifically we have a website that uses cookies (I
> set the cookie to a dictionary) that I would like to convert over to
> sessions becuase osx is not setting my cookie correctly and is making the
> page fail. I am hoping that sessions will work where cookies fail.  Thanks
> in advance for any and all help
> 
> Jose
> 
> 
> 
> 
> -------------------------------------------------------
> 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

Hallo,
jose@... hat gesagt: // jose@... wrote:

> Could someone please point me to a good tutorial on how to use sessions.  I
> have looked at the example docs and the only one that uses session is
> really pretty simple.  Specifically we have a website that uses cookies (I
> set the cookie to a dictionary) that I would like to convert over to
> sessions becuase osx is not setting my cookie correctly and is making the
> page fail. I am hoping that sessions will work where cookies fail.  

Sessions per default require cookies, but you can tell Webware in the
Config file to use path sessions as a fallback. (I never used these,
so: Could someone confirm that it is indeed a fallback solution or
will enabling path sessions remove the - more secure - cookies even if
cookies are accepted by the user?)

In the session itself, you can put basically everything that is
picklabe (even more, but this might lead to strange behaviour). 
A session example is in http://footils.org/pkg/shop.tgz 

ciao
-- 
 Frank Barknecht                               _ ______footils.org__

Thanks for the info, I just made the changes to my site and now the macs
work great using sesssions instead of cookies.

BTW has anyone else had any difficulty setting complex cookies on OSX?

Jose


 -------- Original Message --------
   Subject: Re: [Webware-discuss] sessions
   From: Aaron Held <aaron@...>
   Date: Wed, January 29, 2003 10:53 am
   To: jose@...

   I don't know a good tutorial, but the session class is here:
   http://webware.sourceforge.net/Webware-
0.8b1/WebKit/Docs/Source/Summaries/Session.py.html
   and you can access a session from your servlet via:
   self.session()

   ie:
   #test for a session var:
   	if (self.session().hasValue('sortOn')):
   # pull in a session var (any python object)
   	sortOn=self.session().value('sortOn')
   #pull in a seeson var w/ a default of '0'
   	sortOn=self.session().value('sortOn',0)
   #set a value
   	username='aaron'
   	seld.session().setValue('name',username)
   #delete a value
   	self.session().delValue('name')
   #get sessionID
   	SID = self.session().identifier()

   jose@... wrote:
   > Hi all,
   >
   > Could someone please point me to a good tutorial on how to use
   > sessions.  I have looked at the example docs and the only one that
   > uses session is really pretty simple.  Specifically we have a
   > website that uses cookies (I set the cookie to a dictionary) that I
   > would like to convert over to sessions becuase osx is not setting my
   > cookie correctly and is making the page fail. I am hoping that
   > sessions will work where cookies fail.  Thanks in advance for any
   > and all help
   >
   > Jose
   >
   >
   >
   >
   > -------------------------------------------------------
   > 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

Hallo,
Bogdan hat gesagt: // Bogdan wrote:

> from WebKit.Page import Page
> from Cheetah.Template import Template
> import MySQLdb
> 
> tempDef="""
...
> <TABLE bgcolor="#07e1f9" width=80% align="center">
> <form action="index.py" method=POST enctype="multipart/form-data">
> <input type="text" name="filename"><BR>
> <input type="SUBMIT" name="_action_" value="addrec">
> </form>
> </body></html>
> """
> 
> class index(Page):
>     def __init__(self):
>         Page.__init__(self)
>         self.compTemplate = Template(tempDef)
>     def title(self):
>         return "Test!"
>         
>     def writeContent(self):
>         conn=MySQLdb.connect(db="test", user="root")
>         cur=conn.cursor()
>         cur.execute("""SELECT * from userlist;""")
>         t = self.compTemplate
>         t.row = cur.fetchall()
>         self.writeln(t)
>         cur.close()
>         conn.close()
>         
Your Page-class needs to know about its possible (re)actions to
form input. So just define an "action" and append it to the list of
Page actions like: 

	def actions(self):
		return Page.actions(self) + ['addrec']

	def addrec(self):
		# DB setup...
		req = self.request()
		filename = req.value("filename", None)
		if filename:
			cur.execute('insert into userlist values % ;' %	filename)
		self.writeBody()
ciao
-- 
 Frank Barknecht                               _ ______footils.org__

It looks good, but if you want to use the built-in action handler then
you have to make your SUBMIT button _action_ACTIONAME
like:
<input type="SUBMIT" name="_action_addrec" value="Add A Record">

and then in the servlet:

def actions(self):
		return ['addrec']


def preAction(self,actionName):
	'''Run some code before ANY action'''
	if (self.request().hasField('curPos')):
		curPos = int(self.request().field('curPos'))
	else:
		curPos = 0

def postAction(self,actionName):
	'''Run code AFTER any action'''
	pass

def addrec(self):
	self.writeln(''recodrd added'')


-Aaron
Bogdan wrote:
> I have Webaware 0.7 running on Apache 1.3.26 on Debian linux. I'm a
> newbie in python and webware, and it is difficult for me to browse the
> sources, so can somebody give me an example and/or advice about how to
> handle forms. Here is my code:
> 
> from WebKit.Page import Page
> from Cheetah.Template import Template
> import MySQLdb
> 
> tempDef="""
> <TABLE bgcolor="#07e1f9" width=80% align="center">
> #for $i in $row
>     <tr>
>     #for $k in $i
>         <td>$k</td>
>     #end for
>     </tr>
> #end for
> </table>
> <BR>
> <form action="index.py" method=POST enctype="multipart/form-data">
> <input type="text" name="filename"><BR>
> <input type="SUBMIT" name="_action_" value="addrec">
> </form>
> </body></html>
> """
> 
> class index(Page):
>     def __init__(self):
>         Page.__init__(self)
>         self.compTemplate = Template(tempDef)
>     def title(self):
>         return "Test!"
>         
>     def writeContent(self):
>         conn=MySQLdb.connect(db="test", user="root")
>         cur=conn.cursor()
>         cur.execute("""SELECT * from userlist;""")
>         t = self.compTemplate
>         t.row = cur.fetchall()
>         self.writeln(t)
>         cur.close()
>         conn.close()
>         
> 
> 
> 
> -------------------------------------------------------
> 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

On Wed, 2003-01-29 at 02:12, Costas Malamas wrote:
> Coongrats everybody, I was looking forward to 0.8... BTW, I am probably 
> blind or skimming too much, but what is the *maximum* Python version allowed 
> for Webware?  I've been on 2.1 forever and I am itching to try the new class 
> design...

2.2 works fine, and I expect 2.3 should be the same.

  Ian

No, it still saves the sessions to disk even if you use Memory.  You might
want to use Memory because it is the most efficient of the session stores
(assuming sufficient amounts of memory are available), but still retain the
ability to restart the appserver and preserve sessions.  The naming is
counterintuitive, I'll admit.

We talked about adding an extra option to never store sessions to disk, but
I believe we never did.  Patches welcome...

Another approach would be to add yet another session store "MemoryOnly" or
something like that.

- Geoff

> -----Original Message-----
> From: Stuart Donaldson [mailto:stuartd@...]
> Sent: Tuesday, January 28, 2003 10:30 AM
> To: 'Michael Engelhart'; webware-discuss@...
> Subject: RE: [Webware-discuss] how do i prevent a KeyError on 
> session id
> w hen i restart?
> 
> 
> Not having tried it myself, but I thought you could do this 
> by setting the
> Application.configs setting of 'SessionStore' to 'Memory' 
> rather than the
> default of 'Dynamic'. 
> 
> -Stuart-
> 
> > -----Original Message-----
> > From: Michael Engelhart [mailto:mengelhart@...]
> > Sent: Tuesday, January 28, 2003 7:17 AM
> > To: webware-discuss@...
> > Subject: Re: [Webware-discuss] how do i prevent a KeyError on 
> > session id
> > w hen i restart?
> > 
> > 
> > I still think this should be addressed by putting the 
> ability to NOT 
> > store sessions to disk at all in the configuration parameters.
> > My workaround in 0.7 is to comment out the code that stores Memory 
> > sessions to disk (which in my  mind it should anyway).  
> Memory to me 
> > implies transient, not persistent.  I also believe that storing 
> > sessions to disk is a security hole as well in mnay cases but 
> > that may 
> > just be me.    It would be as easy as changing the Session code to 
> > having Memory Sessions never persist between application restarts.  
> > That way they would just go away after they timed out.
> > 
> > 
> > Mike Engelhart
> > On Tuesday, January 28, 2003, at 09:57  AM, Stuart Donaldson wrote:
> > 
> > > Which version of Webware are you using?
> > >
> > >> From the looks of the trace back you provided, it appears 
> > the problem 
> > >> is
> > > that the decoding of the serialized session on the disk 
> is failing, 
> > > rather
> > > than the session is missing.
> > >
> > > This can be caused by having non-serializable objects in 
> > the Session 
> > > object.
> > > Until recently, the problem would show up just like this, 
> > because the
> > > pickled session object was corrupted since the entire 
> > object could not 
> > > be
> > > stored.
> > >
> > > The current behavior (as of 0.8b1) is to display an error 
> > when trying 
> > > to
> > > pickle the session out to disk, and to not store a 
> > corrupted session on
> > > disk.  The error goes through the 
> > Application.handleException() method 
> > > which
> > > by default will print the message to stdout.
> > >
> > > Note you won't see the pickling exception in your browser because 
> > > there is
> > > no session associated with the error.
> > >
> > > If you are using 0.8b1, please let me know, as there must 
> > be some other
> > > problem.
> > >
> > > But generally I suspect your problem is that you have 
> > something in the
> > > session object which can't be pickled like an open file 
> or database
> > > connection.
> > >
> > > -Stuart-
> > 
> > 
> > 
> > -------------------------------------------------------
> > 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
> > 
> 
> 
> -------------------------------------------------------
> 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
>

On Tue, 2003-01-28 at 09:36, Geoffrey Talvola wrote:
> No, it still saves the sessions to disk even if you use Memory.  You might
> want to use Memory because it is the most efficient of the session stores
> (assuming sufficient amounts of memory are available), but still retain the
> ability to restart the appserver and preserve sessions.  The naming is
> counterintuitive, I'll admit.

Should we rename it to avoid this confusion?  For the foreseeable future
we'd retain Memory with that meaning, but we'd make an alias (no good
ideas at the moment :) and document only that, deprecating the old name.

> We talked about adding an extra option to never store sessions to disk, but
> I believe we never did.  Patches welcome...

I thought that was added, but I wasn't keeping track.  There was a
session corruption patch which wasn't completely applied -- it silently
ignored errors and would have effectively worked like people wanted. 
But it silently ignored errors which wasn't good.

-- 
Ian Bicking           Colorstudy Web Development
ianb@...   http://www.colorstudy.com
PGP: gpg --keyserver pgp.mit.edu --recv-keys 0x9B9E28B7
4869 N Talman Ave, Chicago, IL 60625 / (773) 275-7241

Yes I saw that patch go through but I didn't like the idea of the 
errors just going into the ether and hadn't had time to response until 
now.

It seems to me that since Dynamic does what Memory does (but with the 
added feature of persisting to disk), that we should just keep the term 
Memory and make it transient (i.e, sessions disappear on server 
shutdown or timeout).   I guess I don't really see the need for Memory 
to persist to disk since I can get that capability by using Dynamic 
sessions.   If performance is the real reason to use Memory over 
Dynamic in a certain application, then maybe we should focus on fixing 
the performance problem associated with Dynamic (which I have yet to 
come across myself) instead of moving things around and changing names, 
etc.
I mean the default settings for Dynamic session stores is 10,000 
sessions which I've assumed is an attainable amount before server 
meltdown.  If you're web application has 10,000 open sessions at any 
given time you can probably afford more boxes to cluster your system 
around I would guess.

Personally I like the simplicity of the 3 pronged session approach.  I 
just want if fixed :-)

Mike


On Tuesday, January 28, 2003, at 10:55  AM, Ian Bicking wrote:

> I thought that was added, but I wasn't keeping track.  There was a
> session corruption patch which wasn't completely applied -- it silently
> ignored errors and would have effectively worked like people wanted.
> But it silently ignored errors which wasn't good.

I don't know of any real performance problems with Dynamic.  It's just
theoretically slower because it has to pickle sessions to disk.  By the way,
it doesn't just pickle sessions to disk when it reaches the limit of 10000,
but also after a certain period of inactivity in the session.

Does anyone on the list use the Memory store with the expectation that it
pickles sessions to disk on shutdown?  If not, maybe you're right, we should
just make Memory not save sessions to disk, and document the change very
clearly in the release notes.

- Geoff

> -----Original Message-----
> From: Michael Engelhart [mailto:mengelhart@...]
> Sent: Tuesday, January 28, 2003 11:19 AM
> To: Webware discuss
> Subject: Re: [Webware-discuss] how do i prevent a KeyError on 
> session id
> w hen i restart?
> 
> 
> Yes I saw that patch go through but I didn't like the idea of the 
> errors just going into the ether and hadn't had time to 
> response until 
> now.
> 
> It seems to me that since Dynamic does what Memory does (but with the 
> added feature of persisting to disk), that we should just 
> keep the term 
> Memory and make it transient (i.e, sessions disappear on server 
> shutdown or timeout).   I guess I don't really see the need 
> for Memory 
> to persist to disk since I can get that capability by using Dynamic 
> sessions.   If performance is the real reason to use Memory over 
> Dynamic in a certain application, then maybe we should focus 
> on fixing 
> the performance problem associated with Dynamic (which I have yet to 
> come across myself) instead of moving things around and 
> changing names, 
> etc.
> I mean the default settings for Dynamic session stores is 10,000 
> sessions which I've assumed is an attainable amount before server 
> meltdown.  If you're web application has 10,000 open sessions at any 
> given time you can probably afford more boxes to cluster your system 
> around I would guess.
> 
> Personally I like the simplicity of the 3 pronged session 
> approach.  I 
> just want if fixed :-)
> 
> Mike
> 
> 
> On Tuesday, January 28, 2003, at 10:55  AM, Ian Bicking wrote:
> 
> > I thought that was added, but I wasn't keeping track.  There was a
> > session corruption patch which wasn't completely applied -- 
> it silently
> > ignored errors and would have effectively worked like people wanted.
> > But it silently ignored errors which wasn't good.
> 
> 
> 
> -------------------------------------------------------
> 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
>

> You shouldn't be getting this KeyError after restarting WebKit because
> WebKit is supposed to pickle your sessions to disk when it shuts down, =
and
> load your sessions back in from disk when they are requested after it s=
tarts
> back up.
> =

> Perhaps you're storing something in your session that isn't pickleable?=


yep, i believe that's it.  i've got a DB connection in there.  in another=
 email,
i asked about right way to maintain the db connection.

thanks very much for the help.

-- =

Garry Hodgson                   Let my inspiration flow
Senior Hacker                      in token rhyme suggesting rhythm
Software Innovation Services    that will not forsake me
AT&T Labs                          'til my tale is told and done.
garry@...              =

On Tue, 2003-01-28 at 09:46, Garrett G. Hodgson wrote:
> i bet that's it.  there's a db connection stored in the session().
> what's the right way to maintain a persistent connection, vs. having to connect
> each time?

Probably to put it in a module global, like a dictionary keyed on the
username (assuming the connections are per-user).  You'd have to put in
code to recreate the session if there's no connection in the dictionary
-- like if the AppServer is restarted.  But other than that it should be
pretty simple.

-- 
Ian Bicking           Colorstudy Web Development
ianb@...   http://www.colorstudy.com
PGP: gpg --keyserver pgp.mit.edu --recv-keys 0x9B9E28B7
4869 N Talman Ave, Chicago, IL 60625 / (773) 275-7241

Garrett G. Hodgson wrote:

>>But generally I suspect your problem is that you have something in the
>>session object which can't be pickled like an open file or database
>>connection.
>>    
>>
>
>i bet that's it.  there's a db connection stored in the session().
>what's the right way to maintain a persistent connection, vs. having to connect
>each time?
>
>thanks very much for your help.
>
>  
>
What I am doing is to keep in the Session() object, enough information 
to re-create connections.  Then I have a seperate dictionary that only 
lives in memory which is keyed on the session object to reference data 
which can't be serialized.

I extend my Session object to support this behavior, providing an 
npget() method which retrieves non-persistent session data.   npget() 
also supports an init parameter which allows specifying a function to 
construct the value (ie: open the database) if the key is not already 
present.  This helps readability and allows code like:

    db = session.npget( "DB", init=lambda id=session.userid : 
opendatabase( id ) )

If the database connection does not exist, it executes the init code to 
open the database with the session.userid as the argument.

Should we consider adding something like this to the standard session 
objects?   It might help since we occasionally get people running into 
errors as a result of sticking the database connection on the session 
object directly.

-Stuart-