<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Back button behavior... STATE_SAVING_METHOD? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/back-button-behavior-state-saving-method/m-p/45062#M24988</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Client-side state saving is a "nice idea" in JSF but inherently flawed - it assumes all state is serializable and is &lt;/SPAN&gt;&lt;EM&gt;terrible&lt;/EM&gt;&lt;SPAN&gt; for the performance of the server. The "double post" needed after a Back button is something we have to live with after choosing JSF as our web-development framework The Microsoft .net web-framework also suffers from exactly the same issue, unfortunately it seems to be a common problem of many modern component based web UI frameworks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Aug 2006 08:28:48 GMT</pubDate>
    <dc:creator>kevinr</dc:creator>
    <dc:date>2006-08-16T08:28:48Z</dc:date>
    <item>
      <title>Back button behavior... STATE_SAVING_METHOD?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/back-button-behavior-state-saving-method/m-p/45061#M24987</link>
      <description>Hi,Noticed the behavior of using the browsers back button in the web client.&amp;nbsp; It can get the user confused when the server thinks the user is on a different page.Found the following on http://www.jsf-resources.comIn many cases when using JSF, you?ll notice that the back button does not behave as exp</description>
      <pubDate>Tue, 15 Aug 2006 14:15:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/back-button-behavior-state-saving-method/m-p/45061#M24987</guid>
      <dc:creator>csiege</dc:creator>
      <dc:date>2006-08-15T14:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: Back button behavior... STATE_SAVING_METHOD?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/back-button-behavior-state-saving-method/m-p/45062#M24988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Client-side state saving is a "nice idea" in JSF but inherently flawed - it assumes all state is serializable and is &lt;/SPAN&gt;&lt;EM&gt;terrible&lt;/EM&gt;&lt;SPAN&gt; for the performance of the server. The "double post" needed after a Back button is something we have to live with after choosing JSF as our web-development framework The Microsoft .net web-framework also suffers from exactly the same issue, unfortunately it seems to be a common problem of many modern component based web UI frameworks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Aug 2006 08:28:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/back-button-behavior-state-saving-method/m-p/45062#M24988</guid>
      <dc:creator>kevinr</dc:creator>
      <dc:date>2006-08-16T08:28:48Z</dc:date>
    </item>
  </channel>
</rss>

