On Mon, Apr 30, 2012 at 12:53:41PM -0700, Chris Eppstein wrote: > Rails should enforce the best practices required to keep a user from making > a mistake that would be hard to recover from as their application scales. > An In-Memory queue is good, but it's trivial to build an implementation > that can't be offloaded to another process. So I would like to see this API > *enforce* that all queued objects be serializable/marshal-able at a > minimum. This is a best practice and users who don't like it can trivially > build their own simple queueing solution.
I'm OK with making the default Queue enforce that an object is marshalable. It seems like a good constraint. If they really want an in-memory queue, then they can just switch to ::Queue. > Regarding serializing to non-ruby protocols, I agree this is best left as > an implementation detail. :-) -- Aaron Patterson http://tenderlovemaking.com/
pgpPh25ow1FTI.pgp
Description: PGP signature
