John, I remember the presentation, and in fact my app is built to be a service, so it has some features in common with eRube. I just pulled out my binder to review, and sure enough you mention it.
I think I need to save the POST args as user scope though, since I use the http redirect to check authentication, rather than a TCF. Of course I need to purge these variables after use. And (anticipating a discussion of benefits of using a TCF) there are some reasons why I've implemented this way, including: * avoiding method instantiation on login.taf request * portability to other languages (esp. PHP -- sorry, but I can also use Witango's RAD capabilities to prototype for deployment with other servers) > > >Bill Conlon wrote: > >>I think my basic programming model needs to change, so that the working >>code ALWAYS uses variables. We would need a code snippet at the top of >>each TAF that created variables with the same names as the arguments. >>[Ideally the app server would be optimized so variables created this way >>used a handle or pointer to the underlying argument data, rather than >>being copied]. >> >> >Bill, > >Remember the demonstration i did on eRube at the conference. That's one >of the most important parts of the form handling engine in my opinion. >convertiing all args to locals and always working with locals in the >code makes life very easy. > >/John > >________________________________________________________________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > Bill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
