Streaming and MessageAdaptor's in 2.0

View: New views
1 Messages — Rating Filter:   Alert me  

Streaming and MessageAdaptor's in 2.0

by Daniel Feist :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I looking at the file transport which seems to have three different  
modes each with a different payload:
- streaming: payload=FileInputStream
- payload=byte[] (file contents)
- payload=java.io.File

Currently there is no "streaming.message.adaptor" service descriptor  
property and the MessageAdaptor used for streaming is hardcoded in the  
FileConnector.  Also the FileMessageAdaptor is being used for two  
different payloads; FileInputStream and File.

What I'm wondering is this:

1) Are there also multiple scenarios like this with other transports  
that do streaming or is this unique to the file transport?

2) Should we really be using a separate MessageAdaptor for each  
payload type/scenario or are multiple purpose message adaptors ok?

3) Is there a need to reintroduce the "streaming.message.adaptor"  
service descriptor property?  Or is the file transport an isolated  
case and this is not justified?


Related JIRA'a:
http://mule.mulesource.org/jira/browse/MULE-3198
http://mule.mulesource.org/jira/browse/MULE-3199

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email