Hung Jung Lu wrote: I have been using RAM-based session management for a while, but never wrote a product for it. Since Graham Chiu has mentioned it again about making a real product, I have taken the time to make one, and called it HappySession. :) Well, in short, it uses cookie for session
- Original Message - From: Toby Dickenson [EMAIL PROTECTED] I dont think that's going to fly. It's perfectly ok for a persistant object to contain something that shouldn't be creatable. True enough. Further thought has made me realize that a persistent object could contain only valid
Hello people, could anybode give an example (in code) on subject? Thanks, Mike ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
At 05:07 PM 6/5/00 +0800, Mike wrote: Hello people, could anybode give an example (in code) on subject? This isn't exactly code, but... Set up a LoginManager with a GenericUserSource, and set up the GUS to have users. Make sure that the GUS has a "Persistent Sheet Provider" on the "Sheet
At 12:05 PM 6/5/00 -0400, Evan Simpson wrote: Security is hard :-/ No kidding. And just think, all the hard stuff that's been done to avoid trojans in a portal-ish site can be defeated simply by a user making a page that looks like the portal's login screen and asking the user to "verify"
Eventually, I found that NullResource is the top level class that handles this first (Objectmanager doesn't inherit off of it -- it inherits off of Resource, which would explain why I couldn't override the PUT method). It has a block of logic similar to ObjectManager.PUTer that checks the
As part of making SQLSession transaction-sane, I'd like to be able to specify that something can register itself to be committed or aborted earlier in the list of objects rather than just being put on the end of the list. The reason for this: I want SQLSession to just use a normal DB