|
»
« Return to Thread: Asynchronous transport for permanent connections
Re: Asynchronous transport for permanent connections
by Marco D'Alia
::
Rate this Message:
Sure, I would be happy if my code will become part of Mule, I wrote that
copyright notice for this reason.
I've found that issue in my preliminary work for the thesis, and I know
that this transport can be a pain since some changes from the Tcp
transport are deep, but I hope that someone could find a good use for it.
I'm sorry, the svn repository is: http://minamule.madarco.net/svn
Andrew Perepelytsya ha scritto:
> Marco,
>
> Let me kindly forward you to
> http://mule.mulesource.org/jira/browse/MULE-64
>
> Some legal work - I see this disclaimer on the page:
>
> This program is distrubuted as-is bla bla bla ecc.. and you can do
> whatever you want with it (Public Domain)
>
> Are you willing to give up the copyright in order for the code to
> eventually be incorporated into the Mule codebase? IMNAL, but keep in
> mind your reply may mean a legal agreement.
>
> Sorry for inconvenience, but some housekeeping is a must. And thanks a
> lot for being such a great community member :)
>
> Cheers!
> Andrew
>
> On 3/6/07, * Marco D'Alia* <mule-dev@...
> <mailto:mule-dev@...>> wrote:
>
> Hi,
> I've made a proof of concept of an asynchronous transport for
> permanent
> socket connections as a final thesis for my bachelor degree.
>
> The main objective was to manage a large number of simultaneous
> connections using SEDA, especially with protocols that need to
> keep the
> connections open between requests.
> For this reason I've used non-blocking sockets (through Mina library):
> so while a request is processed there is no thread waiting for a
> response, greatly lowering the number of threads required.
> Looking for a SEDA implementation the choice fell on the excellent
> Mule ESB.
>
> The code is composed of some general classes for implementing
> transports
> with nio and two sample implementations: a sender/receiver tcp
> transport
> and a receiver-only http transport.
>
> This can be useful not only for long lasting/permanent
> connections, but
> also to send large quantities of data, streaming and push protocols.
>
> Since it is based on Mina it can also be useful to integrate Mina
> based
> protocols with Mule.
>
> I've arranged a trac repository with the code and a better description
> of how it works: http://minamule.madarco.net/trac
>
> I'd be glad to hear some feedback from the Mule developer community :)
>
> Marco D'Alia
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
copyright notice for this reason.
I've found that issue in my preliminary work for the thesis, and I know
that this transport can be a pain since some changes from the Tcp
transport are deep, but I hope that someone could find a good use for it.
I'm sorry, the svn repository is: http://minamule.madarco.net/svn
Andrew Perepelytsya ha scritto:
> Marco,
>
> Let me kindly forward you to
> http://mule.mulesource.org/jira/browse/MULE-64
>
> Some legal work - I see this disclaimer on the page:
>
> This program is distrubuted as-is bla bla bla ecc.. and you can do
> whatever you want with it (Public Domain)
>
> Are you willing to give up the copyright in order for the code to
> eventually be incorporated into the Mule codebase? IMNAL, but keep in
> mind your reply may mean a legal agreement.
>
> Sorry for inconvenience, but some housekeeping is a must. And thanks a
> lot for being such a great community member :)
>
> Cheers!
> Andrew
>
> On 3/6/07, * Marco D'Alia* <mule-dev@...
> <mailto:mule-dev@...>> wrote:
>
> Hi,
> I've made a proof of concept of an asynchronous transport for
> permanent
> socket connections as a final thesis for my bachelor degree.
>
> The main objective was to manage a large number of simultaneous
> connections using SEDA, especially with protocols that need to
> keep the
> connections open between requests.
> For this reason I've used non-blocking sockets (through Mina library):
> so while a request is processed there is no thread waiting for a
> response, greatly lowering the number of threads required.
> Looking for a SEDA implementation the choice fell on the excellent
> Mule ESB.
>
> The code is composed of some general classes for implementing
> transports
> with nio and two sample implementations: a sender/receiver tcp
> transport
> and a receiver-only http transport.
>
> This can be useful not only for long lasting/permanent
> connections, but
> also to send large quantities of data, streaming and push protocols.
>
> Since it is based on Mina it can also be useful to integrate Mina
> based
> protocols with Mule.
>
> I've arranged a trac repository with the code and a better description
> of how it works: http://minamule.madarco.net/trac
>
> I'd be glad to hear some feedback from the Mule developer community :)
>
> Marco D'Alia
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Asynchronous transport for permanent connections
| Free embeddable forum powered by Nabble | Forum Help |
