I'm having trouble finding an answer to this one on the rifers.org site, and Google isn't turning it up either:
When I use continuations, how does rife manage the resources associated with storing the execution frame? I'm thinking of using continuations for paging results, and there's no clear end to the paging process, since users can page back and forth through the results. This essentially means that I would have a while(true) loop in the program with a pause in it waiting to receive the next offset from the user. That got me to thinking about continuations and the web, and the fact that there's really no general expectation that a user will come back to any continuation at all, so I know this isn't a unique problem.
So, what does rife do? Does it have a limited size LRU list of all the continuation frames? Weak references to let the JVM free them up as needed? Fixed timeouts?
If there is a resource available on the web that gives this level of detail, I'd really appreciate it if someone would point it out to me.
Thanks,
-Alf
_______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
