I love how the options are Rails Plugin or CGI. If they write their marketing sites in PHP, why didn't they go with PHP instead of the CGI route? Or, is it the case that the CGI was just a "hey, you don't need to use Rails to take advantage of it" ploy?
EDIT: after reading the CGI source, they use some mod_rewrite trickery to avoid running the CGI if theres a cached file.
I originally wrote Sprockets 1) as a replacement for Prototype's build system and 2) as a library that could be used within Rails. Just before releasing 1.0, I added a simple CGI wrapper around the library so we could use it in our marketing sites and so people could use it relatively easily without Rails.
I like the idea of distributing a PHP wrapper. I'll try to add one for the next release.
And there's no "ploy." Interesting theory, though.
Comments
I love how the options are Rails Plugin or CGI. If they write their marketing sites in PHP, why didn't they go with PHP instead of the CGI route? Or, is it the case that the CGI was just a "hey, you don't need to use Rails to take advantage of it" ploy?
EDIT: after reading the CGI source, they use some mod_rewrite trickery to avoid running the CGI if theres a cached file.
I originally wrote Sprockets 1) as a replacement for Prototype's build system and 2) as a library that could be used within Rails. Just before releasing 1.0, I added a simple CGI wrapper around the library so we could use it in our marketing sites and so people could use it relatively easily without Rails.
I like the idea of distributing a PHP wrapper. I'll try to add one for the next release.
And there's no "ploy." Interesting theory, though.
After finding that the CGI was smart, I can see the value in it. The "ploy" comment was written "pre"-enlightenment.