Re: Client-side Caching???
I think I agree with you Andrew. Especially since web-applications often are targeted at a sub-group of users and may carry a stipulation of using a limited range of browsers and setup... Having said that.. the solid MVC architecture in struts can sometimes make me forget I'm programming on the server :-) Cheers, Jon - Original Message - From: Andrew Hill [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Wednesday, November 13, 2002 10:13 AM Subject: RE: Client-side Caching??? A lot of web developers suffer from dhtmlaphobia and wont dare use any form of client side scripting lest it alienate their users who run lynx or netscrap4.x... ;-) (Although to be fair there are still quite a few of the later around. You will also probably hear the excuse that people switch off JavaScript. I reckon such users deserve all they get (or more to the point dont get(though Im sure they dont miss the advertising popups))) Certainly tab effects can be done easily in both ie5 and netscrap6 using styles and script - despite the many many bugs in ns6 in this area... -Original Message- From: Savantraj, Chennamakal Subramanian [mailto:Savant.Rcs;ap.sony.com] Sent: Wednesday, November 13, 2002 17:59 To: 'Struts Users Mailing List' Subject: RE: Client-side Caching??? Why can't you try pure DHTML solutions for providing this kind of effects. Of course you may have to sacrifice cross browser compatibility some times. Just making some hide and show mechanism you can simulate Tab effect easily. -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Wednesday, November 13, 2002 5:49 PM To: Struts Users Mailing List Subject: Re: Client-side Caching??? Hi Eelco, I'm using tiles to create tabbed panes: | A | B C | etc... The user can select any pane to view other aspects of the application.. much like you would do in swing. SO the traversing IS inside the application. Also I put an Apply button on each page then store the page state in a session on the server. So the following works flawlessly: 1)user edits A 2)user applies A (changes are viewed) 3)user selects the B tab - showing the B page 4)user selects the A tab - showing the changed A page. But because nothing happens on the server without the apply.. the scenario does Not work if you leave out step 2. A software engineer wouldn't expect it too.. but a user would - especially coming from using a GUI app. The nature of the program requires as few clicks as possible.. and a lot of information.. It's not really a workflow that I can see cause It's not sequential.. The only way I can see solving this is to use JavaScript to capture edited but un-applied form data behind the scenes. Or reworking the application in someway to enforce the apply. The former feels like an enhancement on the Struts form tags.. which I'm willing to investigate if I'm not barking up the wrong tree! Cheers, Jon - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 9:06 AM Subject: RE: Client-side Caching??? Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application
Re: Client-side Caching???
Hi Eelco, I'm using tiles to create tabbed panes: | A | B C | etc... The user can select any pane to view other aspects of the application.. much like you would do in swing. SO the traversing IS inside the application. Also I put an Apply button on each page then store the page state in a session on the server. So the following works flawlessly: 1)user edits A 2)user applies A (changes are viewed) 3)user selects the B tab - showing the B page 4)user selects the A tab - showing the changed A page. But because nothing happens on the server without the apply.. the scenario does Not work if you leave out step 2. A software engineer wouldn't expect it too.. but a user would - especially coming from using a GUI app. The nature of the program requires as few clicks as possible.. and a lot of information.. It's not really a workflow that I can see cause It's not sequential.. The only way I can see solving this is to use JavaScript to capture edited but un-applied form data behind the scenes. Or reworking the application in someway to enforce the apply. The former feels like an enhancement on the Struts form tags.. which I'm willing to investigate if I'm not barking up the wrong tree! Cheers, Jon - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 9:06 AM Subject: RE: Client-side Caching??? Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: mailto:struts-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
RE: Client-side Caching???
Why can't you try pure DHTML solutions for providing this kind of effects. Of course you may have to sacrifice cross browser compatibility some times. Just making some hide and show mechanism you can simulate Tab effect easily. -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Wednesday, November 13, 2002 5:49 PM To: Struts Users Mailing List Subject: Re: Client-side Caching??? Hi Eelco, I'm using tiles to create tabbed panes: | A | B C | etc... The user can select any pane to view other aspects of the application.. much like you would do in swing. SO the traversing IS inside the application. Also I put an Apply button on each page then store the page state in a session on the server. So the following works flawlessly: 1)user edits A 2)user applies A (changes are viewed) 3)user selects the B tab - showing the B page 4)user selects the A tab - showing the changed A page. But because nothing happens on the server without the apply.. the scenario does Not work if you leave out step 2. A software engineer wouldn't expect it too.. but a user would - especially coming from using a GUI app. The nature of the program requires as few clicks as possible.. and a lot of information.. It's not really a workflow that I can see cause It's not sequential.. The only way I can see solving this is to use JavaScript to capture edited but un-applied form data behind the scenes. Or reworking the application in someway to enforce the apply. The former feels like an enhancement on the Struts form tags.. which I'm willing to investigate if I'm not barking up the wrong tree! Cheers, Jon - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 9:06 AM Subject: RE: Client-side Caching??? Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: mailto:struts-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited
RE: Client-side Caching???
A lot of web developers suffer from dhtmlaphobia and wont dare use any form of client side scripting lest it alienate their users who run lynx or netscrap4.x... ;-) (Although to be fair there are still quite a few of the later around. You will also probably hear the excuse that people switch off JavaScript. I reckon such users deserve all they get (or more to the point dont get(though Im sure they dont miss the advertising popups))) Certainly tab effects can be done easily in both ie5 and netscrap6 using styles and script - despite the many many bugs in ns6 in this area... -Original Message- From: Savantraj, Chennamakal Subramanian [mailto:Savant.Rcs;ap.sony.com] Sent: Wednesday, November 13, 2002 17:59 To: 'Struts Users Mailing List' Subject: RE: Client-side Caching??? Why can't you try pure DHTML solutions for providing this kind of effects. Of course you may have to sacrifice cross browser compatibility some times. Just making some hide and show mechanism you can simulate Tab effect easily. -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Wednesday, November 13, 2002 5:49 PM To: Struts Users Mailing List Subject: Re: Client-side Caching??? Hi Eelco, I'm using tiles to create tabbed panes: | A | B C | etc... The user can select any pane to view other aspects of the application.. much like you would do in swing. SO the traversing IS inside the application. Also I put an Apply button on each page then store the page state in a session on the server. So the following works flawlessly: 1)user edits A 2)user applies A (changes are viewed) 3)user selects the B tab - showing the B page 4)user selects the A tab - showing the changed A page. But because nothing happens on the server without the apply.. the scenario does Not work if you leave out step 2. A software engineer wouldn't expect it too.. but a user would - especially coming from using a GUI app. The nature of the program requires as few clicks as possible.. and a lot of information.. It's not really a workflow that I can see cause It's not sequential.. The only way I can see solving this is to use JavaScript to capture edited but un-applied form data behind the scenes. Or reworking the application in someway to enforce the apply. The former feels like an enhancement on the Struts form tags.. which I'm willing to investigate if I'm not barking up the wrong tree! Cheers, Jon - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 9:06 AM Subject: RE: Client-side Caching??? Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort
Re: Client-side Caching???
Hi Jon, I implemented similar functionality with Struts 1.0.2 (i.e. without tiles). For all tabs together, each containing their own html form fields, I used one form object that was stored in the session. Furthermore, I created an action to which the currently visible html form was posted when changing tabs. This way, it is also possible to validate the input of the current tab when switching tabs and if the validation doesn't succeed, refuse to switch to the next tab. The action will furthermore only cause the form fields in the session form object to be updated, without really applying the changes (e.g. update to the database). Finally, one apply button, will apply the changes on the form object at once. The most important difference with your setup, is that changing tabs causes the visible tab to be submitted to a ChangeTab action. Regards, Eelco Jon Ferguson [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] cc: 13-11-2002 10:48 Subject: Re: Client-side Caching??? Please respond to Jon Ferguson Hi Eelco, I'm using tiles to create tabbed panes: | A | B C | etc... The user can select any pane to view other aspects of the application.. much like you would do in swing. SO the traversing IS inside the application. Also I put an Apply button on each page then store the page state in a session on the server. So the following works flawlessly: 1)user edits A 2)user applies A (changes are viewed) 3)user selects the B tab - showing the B page 4)user selects the A tab - showing the changed A page. But because nothing happens on the server without the apply.. the scenario does Not work if you leave out step 2. A software engineer wouldn't expect it too.. but a user would - especially coming from using a GUI app. The nature of the program requires as few clicks as possible.. and a lot of information.. It's not really a workflow that I can see cause It's not sequential.. The only way I can see solving this is to use JavaScript to capture edited but un-applied form data behind the scenes. Or reworking the application in someway to enforce the apply. The former feels like an enhancement on the Struts form tags.. which I'm willing to investigate if I'm not barking up the wrong tree! Cheers, Jon - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 9:06 AM Subject: RE: Client-side Caching??? Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all
RE: Client-side Caching???
Jon, How does the client jump to page B? If this is done outside the scope of your application (e.g. by selecting a bookmark) there is really not much that can be done about it (I wouldn't speak about an HTML limitation, but rather about a user limitation). If it's done inside the scope of your application (e.g. a button, tab or link you provided), you could easily submit the form to the server (without really applying the changes) and keep the form in your session, for the next time the client selects page A. Regards, Eelco James Mitchell [EMAIL PROTECTED] To: Jon Ferguson [EMAIL PROTECTED] cc: Struts Users Mailing List [EMAIL PROTECTED] 11-11-2002 13:19 Subject: RE: Client-side Caching??? Please respond to Struts Users Mailing List Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: mailto:struts-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
RE: Client-side Caching???
Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: mailto:struts-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
Re: Client-side Caching???
Simple solution is a javascript pop up do you want to save? Combine that with tracking what is the current action .V James Mitchell wrote: Hi Jon, This really belongs on the struts-users mailing list. If you are not already subscribed, you should do so. I'm sending a copy there for further discussion. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens? - Seymour Cray (1925-1996), father of supercomputing -Original Message- From: Jon Ferguson [mailto:ferguson;ieee.org] Sent: Monday, November 11, 2002 6:46 AM To: Struts Developers List Subject: Client-side Caching??? Greetings all, A web-application issue I'm trying to solve: Assume you have a complex web-app that requires links and input between several web-forms. The user can jump around.. and to make the application compelling.. Must be able to. Here's a scenario of interest: 1) User edits page 'A' but does not submit the form 2) User jumps to page 'B' to fill in other details or lookup something 3) User returns to page 'A' expecting to see his edits. Problem: since page 'A' was not submitted the server never saw the edits and so reconstructs the page with the old data. User sees this as a bug (developer sees this as a limitation of HTML!!!). Right now the only clean solution to this kind of problem seems to be: a) use Java with WebStart, b)use Macromedia's Flash with server-side extensions, c)Introduce some sort of client-side caching as part of Strut's Form tags or d)change the layout such that the client-naturally applies changes before proceding. Ideas? Thanks in advanced, Jon -- To unsubscribe, e-mail: mailto:struts-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
Client Side Caching
Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Client Side Caching
As far as I know, you (as a person writing server code) have no control over this. The best you can hope for is that the browser is smart enough to cache the image. One thing I can think of, though, is to make sure that the browser believes that the images are static. Make sure that references to them do not have parameters (for generated images, epecially). E.g. img src=/myapp/images/image1234.gif [GOOD] as opposed to img src=/myapp/imageGenerator?imagenum=1234 [BAD]. I just hypothesizing, though. You could set up a an accelerator between your web server and the outside world, as well. That still won't force browsers to cache images. But, if your images are (infrequently) generated, then an accelerator will cache them and prevent your application/image server from having to generate them constantly for every web hit. Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: August 29, 2002 7:21 AM To: [EMAIL PROTECTED] Subject: Client Side Caching Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Client Side Caching
You could look at using a tablib like OSCache: http://www.opensymphony.com/oscache/ You can cache a whole page or just a part of a page by putting the taglib round the part of the page you want to cache. Works for images and dynamic content. Lisa -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 29 August 2002 12:21 To: [EMAIL PROTECTED] Subject: Client Side Caching Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Client Side Caching
Oops - I just actually read the question. :) OSCache won't do client side caching, but it will stop you actually reloading stuff from the db to serve to people if it hasn't changed. Lisa -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 29 August 2002 12:21 To: [EMAIL PROTECTED] Subject: Client Side Caching Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Client Side Caching
Lisa, I've only glanced at OSCache, but this would be server-side caching, no? -Original Message- From: Lisa van Gelder [mailto:[EMAIL PROTECTED]] Sent: August 29, 2002 9:50 AM To: 'Struts Users Mailing List' Subject: RE: Client Side Caching You could look at using a tablib like OSCache: http://www.opensymphony.com/oscache/ You can cache a whole page or just a part of a page by putting the taglib round the part of the page you want to cache. Works for images and dynamic content. Lisa -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 29 August 2002 12:21 To: [EMAIL PROTECTED] Subject: Client Side Caching Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Client Side Caching
Dittooops! Sorry :-) -Original Message- From: Lisa van Gelder [mailto:[EMAIL PROTECTED]] Sent: August 29, 2002 9:56 AM To: 'Struts Users Mailing List' Subject: RE: Client Side Caching Oops - I just actually read the question. :) OSCache won't do client side caching, but it will stop you actually reloading stuff from the db to serve to people if it hasn't changed. Lisa -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 29 August 2002 12:21 To: [EMAIL PROTECTED] Subject: Client Side Caching Is there a possibility to use Client Side Caching? For example to Save a picture and reload it from the browsers cache, when nothing has changed. or A Page which contains contents from a Database and when nothing has changed on the DB reload the old page from the cache. Thanks Matthias Hanel Matthias Fachinformatiker (Anwendungsentwicklung) in Ausbildung Logistik World GmbH Fon:+49-841-9014-300 Marie-Curie-Strasse 6 Fax:+49-841-9014-302 D- 85055 Ingolstadt mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
