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
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
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
renggli
on 2 Mar 2008 at 8:21The text was updated successfully, but these errors were encountered: