Re: RFC822Marshaller for all content uploaded with FTP/Webdav

On Tue, 2006-05-02 at 14:50 -0300, Sidnei da Silva wrote:
> On Tue, May 02, 2006 at 07:35:16PM +0200, Roché Compaan wrote:
> | I won't have time to write a PLIP and I need to fix this for the client
> | now. I'd like to fix this in a way that might be usable by you.
> | 
> | I am hoping for an implementation that is a bit more intelligent as
> | opposed to just having good defaults. IMO a very simple fix would be to
> | not try to demarshall a file using RFC822Marshaller if it is not
> | appropriate. Maybe even better would be to have an über marshaller that
> | uses RFC882 when appropriate and upload files that are clearly not
> | RFC822 compliant as files, not Plone documents.
> 
> That is exactly what I have in mind.

Actually, thinking about it more, I am more inclined to not have
Marshallers handle more than their name suggest. Would it not be clearer
to decide which marshaller to use in the PUT factory? In addition to
this, all that is needed is to define new marshallers for unknown text
files and binary files.

The decision made in the PUT factory can be made configurable TTW per
mimetype in the mimetypes registry or in an altogether different tool.

>  One small issue is that we must
> *not* read the whole file in memory. Usually reading a small chunk of
> the file should be enough to detect which marshaller should be
> used. This should optimally use the Marshall product to make these
> settings overridable TTW.

I still have to check this out. How does one configure Marshallers using
this product?

-- 
Roché Compaan
Upfront Systems                   http://www.upfrontsystems.co.za



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642