I've been giving some thought to the problem of Middlekit objects in sessions and wanted to get some feedback. Two ways to
1. Proxy. Create a proxy class that wraps the real middlekit object. The proxy would be able to be written to the file store. It would reload the middlekit object when coming of of file. It would pass attribute access and function calls to the contained middlekit object. It would write out the complete objectref id to the file. This is the DogTag pattern we use here, which is varient of the Memento pattern. +only impact to app is when adding object to session -extra level of run-time indirection 2. Fix Middlekit Take above proxy ideas and roll them into the appropriate Middlekit base class. +probably no extra overhead once the object is reloaded -more invasive solution to Middlekit Other thoughts? ===== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kevin Dahlhausen 'Do' or 'do not.' There is no 'Try.' http://members.nccw.net/kdahlhaus/ -Yoda __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
