<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Question for you can I navigate a JSF app. Keep my borwser open, go on vacations, come back and click the next link and get it rendered?<div>If yes, that's RESTable</div><div>If not that's not RESTable (for the purists anyways).</div><div>You need to think Microsoft architecture back in '98</div><div><br></div><div><div><div>On Mar 4, 2009, at 14:41, Dan Allen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Wed, Mar 4, 2009 at 2:23 PM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</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;"> REST kinda mandates to have a stateless application design. Ie the necessary state is always passed through each request. No sure JSF can cope with that.</blockquote><div><br>Why not? JSF's state management is only for the UI ( the component tree). JSF always marshalls the data back and forth through POST. So really if you put the UI aside, it is stateless. There is some gray area, but I think it's feasible to use JSF this way.<br> <br>-Dan</div></div><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> <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></blockquote></div><br></div></body></html>