|
Home > Archive > Perlbal > August 2006 > Perlbal-Long polling Vs Jabber
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Perlbal-Long polling Vs Jabber
|
|
| Prateek Mathur 2006-08-08, 7:11 am |
| What comparison could be there with perlbal long polling(delayed connection
response) vs Jabber, in terms of 1) scalability 2)load balancing capability
3)usage?
Thanks
Prateek.
| |
| Ask Bjørn Hansen 2006-08-08, 7:11 am |
|
On Aug 8, 2006, at 3:08 AM, Prateek Mathur wrote:
> What comparison could be there with perlbal long polling(delayed
> connection response) vs Jabber, in terms of 1) scalability 2)load
> balancing capability 3)usage?
You are comparing a piece of software (perlbal, implementing http)
with a protocol (jabber).
- ask
| |
| Prateek Mathur 2006-08-08, 7:11 am |
| ok I meant a Jabber Server implementation with Perlbal(with long polling) 
Prateek.
On 8/8/06, Ask Bjørn Hansen <ask@develooper.com> wrote:
>
>
> On Aug 8, 2006, at 3:08 AM, Prateek Mathur wrote:
>
>
> You are comparing a piece of software (perlbal, implementing http)
> with a protocol (jabber).
>
>
> - ask
>
>
| |
| Brad Fitzpatrick 2006-08-08, 1:12 pm |
| Still not getting the question.
They're both event-based, using the same underlying framework, so
connections are just as cheap.... neither would be more advantageous.
DJabberd will do long-polling HTTP mode (for Jabber) in time here.
On Tue, 8 Aug 2006, Prateek Mathur wrote:
> ok I meant a Jabber Server implementation with Perlbal(with long polling)=
>
> Prateek.
>
>
>
> On 8/8/06, Ask Bj=F8rn Hansen <ask@develooper.com> wrote:
>
| |
| Artur Bergman 2006-08-08, 1:12 pm |
| The thing that might help us if you say which Jabber Server
implementation.
Cheers
Artur
On Aug 8, 2006, at 5:01 AM, Prateek Mathur wrote:
> ok I meant a Jabber Server implementation with Perlbal(with long
> polling)
>
> Prateek.
>
>
>
> On 8/8/06, Ask Bjørn Hansen <ask@develooper.com> wrote:
>
> On Aug 8, 2006, at 3:08 AM, Prateek Mathur wrote:
>
>
> You are comparing a piece of software (perlbal, implementing http)
> with a protocol (jabber).
>
>
> - ask
>
>
| |
| Prateek Mathur 2006-08-08, 7:11 pm |
| So if djabberd and perlbal are comparable in the way they perform, it could
be better off using djabberd since its easy to integrate ur pieces of
software i.e client to server(C2S) and Server 2Server(S2S) due its xml
protocol and its pluggable nature.
For having perlbal do long polling, may require some changes in perlbal code
so that you could integrate your custom plugin which again is in perl(like
the IMVU folks)? This could be a little difficult for people who dont know
perl.In this aspect jabber has a generic xml protocol to be followed which
could be lot easier?
Let me know if Im wrong anywhere.I'm just trying to analyze what could be
best in what kind of scenario.A head to head comparison.
Perlbal ofcourse could have many other things like internal url routing,
load balancing etc etc..which could be lagging in a jabber implementation.
Whats ideal where and why, thats the real question..
Thanks
Prateek.
On 8/8/06, David Davis <david.davis@gmail.com> wrote:
>
> He's referring to djabberd.
>
>
> David
>
> On 8/8/06, Artur Bergman <abergman@sixapart.com> wrote:
> implementation.
> polling)
>
| |
| Ask Bjørn Hansen 2006-08-08, 7:11 pm |
|
On Aug 8, 2006, at 1:10 PM, Prateek Mathur wrote:
> Whats ideal where and why, thats the real question..
It'd be a lot easier to give you advice if you'd explain what you are
trying to do, rather than which tools you'd like to use.
- ask
--
http://www.askbjoernhansen.com/
| |
| Prateek Mathur 2006-08-09, 7:11 am |
| As the mail subject says its so, im trying to implement a "long polling"
feature in our application-in other words something that "comet" apps try to
achieve.Clients that keep polling the server periodically could affect the
way you scale.So you need a way a to scale and also achieve real time server
updates to the client at the same time.
So basically I need a server that will handle Long polling,support of
thousands of connections/machine,and load balance the connections to the
actual app server where the business logic.
And ofcourse as i mentioned, it should be easy to integrate this
functionality to our existing app server which runs in java.
Other apps Im evaluating are Jetty6.0 which is I guess is in alpha yet.
Hope that shows my requirements better?
Thanks
Prateek.
On 8/9/06, Ask Bjørn Hansen <ask@develooper.com> wrote:
>
>
> On Aug 8, 2006, at 1:10 PM, Prateek Mathur wrote:
>
>
> It'd be a lot easier to give you advice if you'd explain what you are
> trying to do, rather than which tools you'd like to use.
>
> - ask
>
> --
> http://www.askbjoernhansen.com/
>
>
>
| |
| Leon Brocard 2006-08-09, 7:11 am |
| On 8/9/06, Prateek Mathur <mathurprateek@gmail.com> wrote:
> Hope that shows my requirements better?
Much better. Sounds like you want to have a look at cometd:
http://cometd.com/
http://cometd.com/cometd.jpg
Regards, Leon
| |
| Prateek Mathur 2006-08-09, 7:11 pm |
| I had had look on this earlier and I think these folks are still in dev
phase.
Thanks
Prateek.
On 8/9/06, Leon Brocard <acme@astray.com> wrote:
>
> On 8/9/06, Prateek Mathur <mathurprateek@gmail.com> wrote:
>
>
> Much better. Sounds like you want to have a look at cometd:
>
> http://cometd.com/
> http://cometd.com/cometd.jpg
>
> Regards, Leon
>
|
|
|
|
|