Just a follow-up to note that I created an issue for this proposal.<br><br><a href="https://javaserverfaces-spec-public.dev.java.net/issues/show_bugcgi?id=580">https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=580</a><br>
<br>-Dan<br><br><div class="gmail_quote">On Mon, Jun 15, 2009 at 2:41 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000"><br>
So at the surface, it looks like a great way to ensure the user can't
go backwards in the application and redo or undo things they shouldn't
be allowed to do...</div></blockquote></div><div><br>I didn't really envision this mechanism as a way to prevent the user from going backwards. There are much less drastic and more elegant ways to deal with that problem.<br>
</div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000">however, I don't think it guarantees this without
the developer being really careful. What it DOES do, is allow a
sophisticated developer the ability to cleanup state earlier and make
the application much more efficient in how it uses memory.</div></blockquote></div><div><br>Yes, that is the idea. It could be a background thread or perhaps a navigation hook. The developer would have to be aware of the consequences, but I see it more something a framework will leverage. And you could serialize access to the tree to ensure it is not invoked prematurely from a double click (the waiting thread would be able to react to the tree being absent appropriately).<br>
<font color="#888888">
<br>-Dan</font></div></div><div><div></div><div class="h5"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>