Rule 5 - Use ERXThreadStorage instead of the session to have not
so much dependencies there.
I do not use this object, I have seen it proposed as a solution for
things I would have done differently. I would like to see a sample
app that make use of it (simple, just enough to prove the
concept). Maybe just expose a situation where it solve a common
problem in an efficient way.
An example where I use ERXThreadStorage is that when a user
authenticates, I put the user into thread storage. The particular
case where this is useful is in our notification framework (which
emails and instant-messages people about changes). In this case,
model objects are actually firing these notifications, and the
notification system needs to know who the current user is (to do
things like "don't notify me about something i did" as well as to
know who actually made the change). So it can get the current user
out of thread storage and I don't have to pass a bunch of session/
user stuff down through every single layer of the API (and some
places you just can't get to it -- for instance, a notification out
of of the EO update delegate methods).
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
