Tuesday, January 26, 2016
Using web workers in Rails seems a little awkward. I was wondering if anyone had a nice work flow.
-- 1) Since they are loaded directly, they can't be in the asset pipeline, so I created a folder under public: public/web_workers/
Disadvantages:
- The web worker code isn't minimized.
- The web worker code is not where all the other javascript files are, so it is a little bit "hidden" during development.
- The web worker code doesn't get the fingerprint, so I've had some issues with the browser caching the old code.
Can anyone improve on this system?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CABceSpBtBtVm2kmEfdfNV95aqLndoN6UrGe%3D9HbhGdCboV1VYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment