Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add switch to WAFileLibrary such that #/ also generates static paths #9

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 17 comments

Comments

@GoogleCodeExporter
Copy link

I would suggest to leave WAFileLibrary as it is in 2.8, but provide the ability 
to toggle the behavoir 
of #/ to generate url between (a) the current way - served by Seaside, and (b) 
another static path.

This way, resources can continue to be versioned in MC. For smaller deployments 
or quick testing 
purposes, (a) can be used without requiring any additional set up. (b) can be 
used to serve the 
resources via KOM, Swazoo, httpd, etc. Other than for production/efficiency 
purposes, a key 
advantage of (b) is that during development, changing a JS/CSS file on disk 
will instantly reflect 
upon browser refresh...

Additional interfaces such as FTP/webdav access can simply be built on top of a 
static file, via (b).
Steps To Reproduce  

Original issue reported on code.google.com by renggli on 2 Mar 2008 at 8:21

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant