danial_thom at yahoo.com
Fri May 13 09:52:44 PDT 2005
--- Joshua Coombs <jcoombs at xxxxxxx> wrote:
> > As a "network engineer", you should know that
> > internet in general doesn't guarantee
> > packet delivery. So any application that
> > handle it is simply unreliable on the
> > If an application requires in-order delivery,
> > can direct the traffic to use a single link.
> > you can't guarantee what happens once its out
> > your network. So without a transport layer
> > application is just a crapshoot.
> > You have all sorts of load-balancing going on
> > throughout the internet, and almost none of
> > guarantees in-order delivery. So if you
> > your own link thinking that you're going to
> > something work, then you just don't
> > the big picture.
> > Danial
> I'm fully aware of that. Inside my network,
> I'm performing VoIP, and
> at some points in my network, there are
> multiple point to point paths.
> Rather than clamp VoIP to one of those paths,
> and have to correct for
> it when it breaks, I rather just use a feature
> of one of my transport
> options to make things behave the way I need
> them to. I don't
> consider this sabotage, rather (repeat warning)
> using the right tool
> for the job. CPU and Memory are cheap and
> managable, links where I
> need them are expensive, and take time to push
> through from order to
> carrying data.
> I like options and choice, please don't take
> that away just because
> you only prefer one methodology.
> My vote: If DFly can support both, great. If
> not, support whichever
> provides the most functionality and
Well since the number of sites using PPP are
probably 10,000 to 1 vs MPP, I'd vote for PPP.
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
More information about the Users