[JDEV] UDP vs TCP

[ltherond@elitehill.com -- pop account]

----- Original Message -----
From: <mark at mjwilcox.com>
To: <jdev at jabber.org>
Sent: Friday, September 01, 2000 6:32 AM
Subject: Re: [JDEV] UDP vs TCP


> The basic message is still valid. TCP, at least at the moment, is
> still the better choice for implementing Jabber because TCP will
> give us good enough performance, with a lot less work and we'll
> worry about massive scaling later.

I disagree. TCP makes poor use of today's networks.
How many times do you think a message should get onto the wire?
n times through n TCP connections, or once via a broadcast/multicast?

> Here were are, just a few months after 1.0 release, still trying to
> figure out all of the Jabber protocol compoments. What works,
> doesn't work, etc in the protocol itself.
>
> And people are already worrying about optimizations. Obtuse
> Optimization should come last in any project. First we need
> working, readable code/protocol.

I agree on that, but TCP doesn't make things easier.
Shouldn't we find a way to abstract the transport layer? Using a plug-in
architecture?

> Then we can move on to optimization. As temas pointed out,
> Jabber is just a protocol. If you want to run it over UDP, give it a
> shot. Hell, if you want to run it over Appletalk, give it a shot :).

Hey, look at this! The same thought...

> This is an open-source software project. Instead of blabbing on a
> listserv, that we're stupid and wouldn't know how to make a "hello
> world" program without your hand-holding, give us some code!

Ooooooooooo! That was a little mean! :-)

Problems have solutions...if you can remain open to them.