Problem with CSS and caching
We are currently using GWT for a medium size project. Currently we are facing couple of issues one issue has to deal with CSS cache, when our Interface developer team try to debug a certain CSS issue and they modify the CSS on deployed war, they don't see the result of changes right away rather it takes few minutes to see the result. My question is does GWT has some sort of cache mechanism? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Problem with CSS and caching
Thanks every body, I reckon that was the case but was not sure since i am new to GWT and this is our first application. GWT does not lend it self very well to separation of form from function on client side and when it comes to division of labor, java is not the first pre-requisite for Interface people and I guess reverse is true in regards to CSS for java developers. Thanks though! On Sep 23, 11:52 am, Thomas Broyer [EMAIL PROTECTED] wrote: On 23 sep, 02:41, p4r1tyb1t [EMAIL PROTECTED] wrote: We are currently using GWT for a medium size project. Currently we are facing couple of issues one issue has to deal with CSS cache, when our Interface developer team try to debug a certain CSS issue and they modify the CSS on deployed war, they don't see the result of changes right away rather it takes few minutes to see the result. My question is does GWT has some sort of cache mechanism? GWT doesn't do anything with CSS stylesheets (apart from injecting them in the host page when they're declared in your module's *.gwt.xml), let alone any kind of caching. (not talking about CssResource from GWT-Incubator here, just plain old GWT) There must be some caching directive on your server (Expires, max-age, etc.). When doing such testings, if I were you, I'd configure my browser to always consider its own cache stale (always check for newer versions in IE's parlance, switch network.http.use-cache to false in about:config in Firefox, etc.) and/or use Ctrl+F5 to refresh the page. Or change the configuration on your server, but it has an impact on performances (so if you're using your server to test the app and appreciate the user experience...) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Problem with CSS and caching
Thanks every body, I reckon that was the case but was not sure since i am new to GWT and this is our first application. GWT does not lend it self very well to separation of form from function on client side and when it comes to division of labor, java is not the first pre-requisite for Interface people and I guess reverse is true in regards to CSS for java developers. Thanks though! On Sep 23, 11:52 am, Thomas Broyer [EMAIL PROTECTED] wrote: On 23 sep, 02:41, p4r1tyb1t [EMAIL PROTECTED] wrote: We are currently using GWT for a medium size project. Currently we are facing couple of issues one issue has to deal with CSS cache, when our Interface developer team try to debug a certain CSS issue and they modify the CSS on deployed war, they don't see the result of changes right away rather it takes few minutes to see the result. My question is does GWT has some sort of cache mechanism? GWT doesn't do anything with CSS stylesheets (apart from injecting them in the host page when they're declared in your module's *.gwt.xml), let alone any kind of caching. (not talking about CssResource from GWT-Incubator here, just plain old GWT) There must be some caching directive on your server (Expires, max-age, etc.). When doing such testings, if I were you, I'd configure my browser to always consider its own cache stale (always check for newer versions in IE's parlance, switch network.http.use-cache to false in about:config in Firefox, etc.) and/or use Ctrl+F5 to refresh the page. Or change the configuration on your server, but it has an impact on performances (so if you're using your server to test the app and appreciate the user experience...) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
