You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Paul Hammant <Pa...@yahoo.com> on 2002/02/27 15:51:57 UTC
Re: [AltRMI] (PATCH) BEEP wire
Vinay,
Committed dude. When you next do a zip of source for me, can you leave
out the cvs dirs ;-) Cheers dude :-)
>Hi Paul,
>....Presenting the BEEP transport layer for AltRMI
>....
>
>NEW PACKAGES:
>org.apache.commons.altrmi.client.impl.beep.*
>org.apache.commons.altrmi.server.impl.beep.*
>
>For now I have built an independent test
>suite(BeepClient/ServerTest),
>but I guess this can be merged onto
>SocketClient/ServerTest suite too ....
>
>Ant script puts the /lib folder into the classpath
>, and thats where the beep library (beepcore.jar)
>& xerces wud go ..
>(Haven't attached the libraries here though .)
>
>tests2.xml have been updated with the
>'beep-serve' and 'beep-client' targets too ..
>(This time I have NO batch files :-)) )
>
he he :-)
>We can benchmark it with Socket layer too.
>(It might performs well too compared to
>the '2 socket connection' approach when
>callbacks come into picture..)
>
I see that you have a complete BEEP Factory and HostContext. That's a
lot of work you have done. Some reading for me to do later!
Question for others : If we include a BSD licensed jar (to compile
against and resitribute) do we have to include it's license too... or
just credit the origin.
Regards,
- Paul
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [AltRMI] (PATCH) BEEP wire
Posted by vinaysahil chandran <sa...@yahoo.com>.
Paul,
My understandin was that XML exchanges were
carried out to establish a session and henceforth
its header+payload traveling back and forth..
I admit there would be some extra header info
being passed here and there and
moreover some sync' issues , but never
expected the performance to this low.
I shall _try_ looking into BEEP more.
The work I did was a quick craft
of what I could gather from a lone example and the RFC
.
But as u mentioned writing our-own custom
Multiplexer or the one from sourceforge
(hope there are no license issues ) can be our other
options ..
Regards,
V i n a y.
--- Paul Hammant <Pa...@yahoo.com> wrote:
> Vinay,
>
> >Hi Paul,
> >We need a xml parser too along with beep
> libraries,
> >since BEEP exchanges xml messages
> > between peers to manage the channels/sessions
> >between the peers .
> >So maybe we can put xerces in /lib folder too..
> >
> I did not know it depended on XML parsing. It's
> only a multiplexer of
> byte streams, why did they need XML? Something
> lower tech would have
> been more appropriate.
>
> >Another favor , can you try benchmarking
> >BEEP with others in your 'PROPOSAL' .
> >Lets see how that fares as well .. ..
> >(I think it should do pretty well)
> >
> Well here is the speed:
>
> CustomStream over BEEP over sockets - 1000
> invocations per second
>
> Compare that to:
>
> CustomStream over sockets 8000 per second.
> ObjectStream over sockets 10000 per second.
>
> I think the speed is fairly poor. I was expecting a
> 10% speed drop, but
> this is 90% Vinay. Thatnks for doing the
> integration, Vinay, but I
> think we'll be evolving our own multiplexer that is
> faster. I have had
> a quick look and cannot see a flush() method that
> may speed it up.
>
> What are you thoughts dude?
>
> Regards,
>
> - Paul
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [AltRMI] (PATCH) BEEP wire
Posted by Paul Hammant <Pa...@yahoo.com>.
Vinay,
>Hi Paul,
>We need a xml parser too along with beep libraries,
>since BEEP exchanges xml messages
> between peers to manage the channels/sessions
>between the peers .
>So maybe we can put xerces in /lib folder too..
>
I did not know it depended on XML parsing. It's only a multiplexer of
byte streams, why did they need XML? Something lower tech would have
been more appropriate.
>Another favor , can you try benchmarking
>BEEP with others in your 'PROPOSAL' .
>Lets see how that fares as well .. ..
>(I think it should do pretty well)
>
Well here is the speed:
CustomStream over BEEP over sockets - 1000 invocations per second
Compare that to:
CustomStream over sockets 8000 per second.
ObjectStream over sockets 10000 per second.
I think the speed is fairly poor. I was expecting a 10% speed drop, but
this is 90% Vinay. Thatnks for doing the integration, Vinay, but I
think we'll be evolving our own multiplexer that is faster. I have had
a quick look and cannot see a flush() method that may speed it up.
What are you thoughts dude?
Regards,
- Paul
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [AltRMI] (PATCH) BEEP wire
Posted by vinaysahil chandran <sa...@yahoo.com>.
Hi Paul,
We need a xml parser too along with beep libraries,
since BEEP exchanges xml messages
between peers to manage the channels/sessions
between the peers .
So maybe we can put xerces in /lib folder too..
Another favor , can you try benchmarking
BEEP with others in your 'PROPOSAL' .
Lets see how that fares as well .. ..
(I think it should do pretty well)
Thanks,
V i n a y
--- Paul Hammant <Pa...@yahoo.com> wrote:
> Vinay,
>
> Committed dude. When you next do a zip of source
> for me, can you leave
> out the cvs dirs ;-) Cheers dude :-)
>
> >Hi Paul,
> >....Presenting the BEEP transport layer for AltRMI
> >....
> >
> >NEW PACKAGES:
> >org.apache.commons.altrmi.client.impl.beep.*
> >org.apache.commons.altrmi.server.impl.beep.*
> >
> >For now I have built an independent test
> >suite(BeepClient/ServerTest),
> >but I guess this can be merged onto
> >SocketClient/ServerTest suite too ....
> >
> >Ant script puts the /lib folder into the classpath
> >, and thats where the beep library (beepcore.jar)
> >& xerces wud go ..
> >(Haven't attached the libraries here though .)
> >
> >tests2.xml have been updated with the
> >'beep-serve' and 'beep-client' targets too ..
> >(This time I have NO batch files :-)) )
> >
> he he :-)
>
> >We can benchmark it with Socket layer too.
> >(It might performs well too compared to
> >the '2 socket connection' approach when
> >callbacks come into picture..)
> >
> I see that you have a complete BEEP Factory and
> HostContext. That's a
> lot of work you have done. Some reading for me to
> do later!
>
> Question for others : If we include a BSD licensed
> jar (to compile
> against and resitribute) do we have to include it's
> license too... or
> just credit the origin.
>
> Regards,
>
> - Paul
>
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>