This is quite informative. I am still digesting Pettyjohn's paper but I get the spirit of how it works without grokking the details at this time. I will have to dig more and by then will have more questions ;) <br><br>
Thanks,<br>yinso <br><br><div><span class="gmail_quote">On 5/3/07, <b class="gmail_sendername">Jay McCarthy</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 5/3/07, YC <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<br>> Thanks Jay, this is quite interesting (sounds almost like black magic). Are<br>> you using web cells to store the continuation marks that you can use to
<br>> recreate the continuation?<br><br>Yes. But for different types of information I find parameters useful.<br><br>> What type of information do you lose (since you<br>> say the the continuation is coarse) in this case?
<br><br>For example, if you click on a button to change the sort of the list<br>and the continuation is dead, then you get back the list without the<br>sort being changed. Similarly, if there was form data with the<br>request, it is ignored, as I do not capture what was meant to be done
<br>with it.<br><br>> I meant to ask that are<br>> there types of continuations that shouldn't be reconstructed this way so the<br>> program functions correctly.<br><br>Any type of continuation capturable in the Pettyjohn paper would be
<br>able to be captured like this, however, I had the constraint of<br>writing the capturing code by hand in the application, and I made a<br>pretty low threshold on the amount of pain I was willing to suffer.<br>The users don't complain. Much.
<br><br>Jay<br><br>--<br>Jay McCarthy <<a href="mailto:email@example.com">firstname.lastname@example.org</a>><br><a href="http://jay.teammccarthy.org">http://jay.teammccarthy.org</a><br></blockquote></div><br>