For those that couldn't see my previous message because of its MIME
attachement, here's the text of it. If you wan the example I mention,
let me know.
d
-----------------
How about this:
override createSession() on the Application and put just the SessionID
into an array. You can then use woapp api to get the session. In your
Session finalize method you can remove the ID from this list. I put
together a little bitty test example... BE CAREFUL. If you try to
checkout a session that you are currently in you could deadlock, leak,
or worse. Also if did this in a real app, you'd probably only want like
one user ever doing this OR better have only processing in the
Application doing this, perhaps via an order from a DirectAction or a
NSTimer. Having Sessions manipulating other Sessions seems like a really
interesting problem space I'd like to avoid with multiple threads going
concurrently.
The example app keeps a list of session IDs and displays this list in
the Main page. You can pick a ID to 'inspect' and the thing grabs the
session from the session store (w/o locking it BTW, you might want to!)
shows its creation date.
d
David Neumann wrote:
