You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We started using LocalStorage in our app which has lead to some problems with the seoserver, particularly when we decided to change the default values we use in one of our LocalStorage models or when one url changes the values in LocalStorage which then effects another request.
I'd like to setup the seoserver to clear LocalStorage with each request. PhantomJS stores it's LocalStorage data in a file on the filesystem which is configurable via the --local-storage-path command line option (http://phantomjs.org/api/command-line.html).
I'm thinking in lib/seoserver.js:getContent when spawning the new phantomjs process a unique --local-storage-path could be generated and used for each child process, and then removed during the exit event. Starting up the server could also clear out any LocalStorage files that managed to linger around.
Thoughts?
The text was updated successfully, but these errors were encountered:
We started using LocalStorage in our app which has lead to some problems with the seoserver, particularly when we decided to change the default values we use in one of our LocalStorage models or when one url changes the values in LocalStorage which then effects another request.
I'd like to setup the seoserver to clear LocalStorage with each request. PhantomJS stores it's LocalStorage data in a file on the filesystem which is configurable via the
--local-storage-path
command line option (http://phantomjs.org/api/command-line.html).I'm thinking in
lib/seoserver.js:getContent
when spawning the new phantomjs process a unique--local-storage-path
could be generated and used for each child process, and then removed during theexit
event. Starting up the server could also clear out any LocalStorage files that managed to linger around.Thoughts?
The text was updated successfully, but these errors were encountered: