On Sat, 3 Apr 2004, Gisle Aas wrote: > Joshua Hoblitt <[EMAIL PROTECTED]> writes: > > > > 1) Is this a good idea? > > The usecase for this seems a bit unclear to me. How would you use > this module? I don't understand what needs handling of multipart > responses requires.
An example would be handling the response to a request that had multiple 'Ranges' of a resource. > > 2) Is HTTP::Multipart a good name? > > I think all that would be needed for this is a method on > HTTP::Message. It could for instance be called 'parts'. If the > method is not too long and generally useful then it should just go > into that module. Sounds reasonable. I'll submit a patch. > > 5) if a class method is sufficient, would should it's name be? > > (ie., C<parase>?) > > What does 'parase' mean? It means I tried to type 'parse' before having my morning coffee. :) -J --
