Creating "Buffers" - problems with history and coookies — OZONE Asylum, home of the Mad Scientists

DHTML/Javascript

Creating "Buffers" - problems with history and coookies

This page's ID: 28018

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	It seems like you are talking about [url=http://en.wikipedia.org/wiki/Continuation]continuation[/url] management. At work we use Cocoon which handles the whole state machine aspect of this. Maybe a little discussion on how Cocoon handles their continuations might give you an idea on how you would want to set things up. Just a little note, in the application we have created there are areas where messages get confused. We are using a mess of nested iframes with areas that spawn new windows and processes that happen in parallel so many systems will have trouble attaching a message where you want it all the time. The trouble is actually the developer not coding things correctly, but just saying that it can be confusing even when using a somewhat developed framework. With a continuation each request gets its own continuation id, and the continuation manager which controls the creation and destruction of all of the active states. The easy way to look at this is that each different request creates a different id and a copy of all associated variables, when coming back through on a request (when the user presses submit) the continuation id is also sent and used in combination with all of its associated session values (such as lastmessage). This is all done in memory without saving to the database. There might (and probably are) disk writes that are happenning but that is all controlled by the serialization mechanism of the server. Another thing to note is that not all pages use a continuation, only those that will need to keep track of data related to the current request chain. An overview might look something like - [img]http://www.codetown.org/examples/simple-continuation.png[/img] As you can see each page has a display, which is the message that is currently being shown, then there is the id of the page which is stored on the page (either as part of the form's submit URL or in a hidden field), the current page when submitted will create a message m, which is the message that will be displayed on following pages. What this gives you is the easy use of back and forward (well at least back as forward in a submission process tends to resubmit the data) which will take you to a page that has an id embedded in the page. Since all of your local data is associated with an id and you can easily tell which message belongs to who by keeping track of each continuations parent. What this does (that your method does not) is keep a whole lot of garbage data present, as you will be spawning continuations that will all have to live for the life of the user's session (or you will have to develope a garbage collection scheme). I know that all of this writing doesn't directly solve your problem in a if you do X you will be set kind of way. I don't think I could give you a direct solution without seeing your code as just using words relegates this to an exercise in theory. You are attempting to do something that a lot of bright people are spending their time working on, kudos in that respect. Dan @ [url=http://www.codetown.org]Code Town[/url] [small](Edited by [url=http://www.ozoneasylum.com/user/191]WarMage[/url] on 06-01-2006 03:57)[/small] Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu