Mark Baker wrote:
> On 6/28/06, Stefan Tilkov <[EMAIL PROTECTED]> wrote:
>
>>That said, I do believe RMI is a tightly coupled technology that
>>should only be used (in the mainstream way) for systems, usually
>>single applications, where tight coupling is acceptable (very few, in
>>my experience). Unless, of course, you do use RMI to pass documents
>>-- which one can do, but is rarely done.
>
> Right, in part because the performance would suck. It's optimized for
> method invocation, not data transfer.
It depends on what you do with it. I have a set of classes that I use on a
regular bases to do high performance data streaming out of RMI. My RMI calls
return an InputStream. Through the use of mobile, the interface defined API
looks like:
public interface MyInterface {
... some other methods ...
public InputStream transferSomething( SelectionCriteria data );
}
The returned InputStream is actually an Serializable object which connects back
to the server using data provided in the serialized form. The client then
calls
read et.al. on the InputStream which is intern forwarded to the Socket that
goes
back to the server. Presto, you have socket based streaming in an RMI call.
The performance is great and I didn't have to break the programming model to
meet the performance needs of the client. I did it all with mobile code that
the service architect decided on the implementation of.
Gregg Wonderly
------------------------ Yahoo! Groups Sponsor --------------------~-->
Great things are happening at Yahoo! Groups. See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
