Aaron Held wrote:In webware or asp if you want to store customerID you just add CustomerID=1234 to the session. But if you are using a shared database you may want to setup a field called customerID. This has the added advantage of being usable by any app as well as something that you can easily report on. (such as 'abandoned cart contents' reports)
The real problem is that webware wants to pickle the data, so you can create and delete session values on the fly. If you map to a database then all of the fields will have to be know.
Don't understand this. What do you mean by "fields will have to be know"? If I write custom session manager could it override Webware request for pickling/unpickling session's data?
On the other hand it make development a bit slower since every time you need another varirable stored in the session you have to modify the database.
If you encode the key=values in some independant format then you avoid this.
I guess that you could also use some string encoding system (maybe convert value - pairs into a POST or GET string - supported on both servers)
Yes, I was thinking about this.
BTW I have used both the wkCGI.exe and the isapi filter w/ IIS successfully in the past. They ISAPI filter may have had some memory issues, but wkCGI.exe was fast enough so I used that in production.
-Aaron
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
