# Rails big pain - uploads and plugin versioning

**URL:** <https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554>\
**Category:** Rails\
**Created:** [December 9, 2007, 10:17am UTC](https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554 "2007-12-09T10:17:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nowy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/bc8723/32.png) [@Nowy](https://www.ruby-forum.com/u/Nowy)\
**Post date:** [December 9, 2007, 10:17am UTC](https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554/1 "2007-12-09T10:17:40Z")

</div>

First of all, congratulations, for rails 2.0 !.  
I just want to ask two short questions:

1. Any plans to improve file uploads ? (now single upload block my  
entire mongrel process) Or any alternatives ?
2. What about plugin versioning ? Now we have rails 2.0, it would be  
reasonable to do plugin versioning like i.e. does for its extensions  
so every plugin applies only to a specific version(s) of application.

---

<div class="post-metadata">

**Author:** ![Nowy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/bc8723/32.png) [@Nowy](https://www.ruby-forum.com/u/Nowy)\
**Post date:** [December 9, 2007, 3:40pm UTC](https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554/2 "2007-12-09T15:40:26Z")

</div>

On 9 Dec 2007, at 09:17, Nowy wrote:

> First of all, congratulations, for rails 2.0 !.  
> I just want to ask two short questions:
> 
> 1. Any plans to improve file uploads ? (now single upload block my  
> entire mongrel process) Or any alternatives ?

not something I’ve ever used

> 1. What about plugin versioning ? Now we have rails 2.0, it would be  
> reasonable to do plugin versioning like i.e. does for its extensions  
> so every plugin applies only to a specific version(s) of application.

I believe the long term future here lies in gems (ie plugins that are  
gems). gems already have versions, locking to specific versions/ranges  
etc… so it makes sense to leverage this rather than rewrite it.

Fred

---

<div class="post-metadata">

**Author:** ![Nowy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/bc8723/32.png) [@Nowy](https://www.ruby-forum.com/u/Nowy)\
**Post date:** [December 9, 2007, 6:30pm UTC](https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554/3 "2007-12-09T18:30:01Z")

</div>

> > 1. What about plugin versioning ? Now we have rails 2.0, it would be  
> > reasonable to do plugin versioning like i.e. does for its extensions  
> > so every plugin applies only to a specific version(s) of application.
> 
> I believe the long term future here lies in gems (ie plugins that are  
> gems). gems already have versions, locking to specific versions/ranges  
> etc… so it makes sense to leverage this rather than rewrite it.

Also note that all plugins coming off SVN repositories implicitly has  
version numbers. And if you’re using something like Piston to manage  
your SVN externals, it’s really easy to tie yourself to a given SVN  
version.

That being said, I’m not necessarily against a more formal scheme. I  
just haven’t felt much, if any, pain from the current setup.

---

<div class="post-metadata">

**Author:** ![Nowy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/bc8723/32.png) [@Nowy](https://www.ruby-forum.com/u/Nowy)\
**Post date:** [December 9, 2007, 8:29pm UTC](https://www.ruby-forum.com/t/rails-big-pain-uploads-and-plugin-versioning/122554/4 "2007-12-09T20:29:06Z")

</div>

DHH wrote:

> > > 1. What about plugin versioning ? Now we have rails 2.0, it would be  
> > > reasonable to do plugin versioning like i.e. does for its extensions  
> > > so every plugin applies only to a specific version(s) of application.
> > 
> > I believe the long term future here lies in gems (ie plugins that are  
> > gems). gems already have versions, locking to specific versions/ranges  
> > etc… so it makes sense to leverage this rather than rewrite it.
> 
> Also note that all plugins coming off SVN repositories implicitly has  
> version numbers. And if you’re using something like Piston to manage  
> your SVN externals, it’s really easy to tie yourself to a given SVN  
> version.
> 
> That being said, I’m not necessarily against a more formal scheme. I  
> just haven’t felt much, if any, pain from the current setup.

i never know gems were locked into specific version ranges.  
so, with all the depreciated things, you are saying i can’t  
get stuck, installing an old gem that has a lot of depreciated things?
