> method, the competing servers would clobber each other's data. > > Make sense?
Yes, perfectly. I didn't think of this yet and would have detected this when testing or even later... embarrassing... > BTW I mix-in the following methods to MiddleObject for my WebKit > applications. The "value=..." above comes from invoice.formArg(). I've added them, thanks a lot. I think there should be a place in the web (in Webware space) or in the Webware docs itself, which shows all these common practices, or how-tos, or tips & tricks or however you want to call these pearls of knowledge. These would be invaluable especially for those not being able working full time on their Webware apps (like me) and not having any CGI background (again like me: I wanted to avoid plain CGI programming, had a look at Zope, saw that that's a waste of time at least for me and was - thank god - pointed to Webware by you). Am I the only one missing this? From the various postings on this list I know that there are many coming from other web-app-frameworks. But this does not apply to me. Hey, come on, there must be more beginners like me... Best regards and many thanks again Franz > -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im Auftrag von Chuck > Esterbrook > Gesendet: Freitag, 26. Oktober 2001 23:19 > An: [EMAIL PROTECTED] > Cc: Webware-discuss > Betreff: Re: AW: [Webware-discuss] Design Question > > > At 04:51 PM 10/26/2001 +0200, F. GEIGER wrote: > >These would be single variables and single variables can be stored in > >sessions too. I prefer session data and resort to hidden fields only if I > >have to identify single elements within a bunch of them. Isn't > this common > >practice? Don't you store your volatile data in the session? > Should I change > >my habits here too? > > The only thing that comes to mind is if the user were to open 2 browser > windows to perform the same type of operation with different data at the > same time. The form fields method would work fine. I think with > the session > method, the competing servers would clobber each other's data. > > Make sense? > > > But instead of carrying all the fields in your multi-form > process, making a > new instance in each should work fine. Then in the form, you just pass a > reference to the object that is being edited: > <input hidden name=object value=Invoice.8> > > BTW I mix-in the following methods to MiddleObject for my WebKit > applications. The "value=..." above comes from invoice.formArg(). > > class MiddleObjectMixIn: > > def formRef(self): > return '"%s.%i"' % (self.klass().name(), > self.serialNum()) > > def formArg(self): > return 'value=%s' % self.formRef() > > def urlRef(self): > return '%s.%i' % (self.klass().name(), self.serialNum()) > > def urlArg(self): > return 'object=%s' % self.urlRef() > > from MiddleKit.Run.MiddleObject import MiddleObject > from MiscUtils.MixIn import MixIn > MixIn(MiddleObject, MiddleObjectMixIn) > > > > -Chuck > > > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
