Re: peer to peer messaging
- From: "Tim Ward" <tw2@xxxxxxxxxxxx>
- Date: Thu, 26 May 2005 16:40:00 +0100
"Guy Noir" <ahackney@xxxxxxxxx> wrote in message
news:1117119994.504588.45180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Start with 2 machines on the same subnet. Get your services working and
> then work your way out to dealing with NAT issues.
Coo! That's clever! Then when you find that your system architecture cannot
be extended to work across NAT boxes you just go to your boss and/or client
and tell them that you've wasted your time and their money so far, now you
need to start again from scratch to design a system that's actually going to
be useful!
Not a career-enhancing approach, I would suggest.
--
Tim Ward
Brett Ward Limited - www.brettward.co.uk
.
- Follow-Ups:
- Re: peer to peer messaging
- From: Chris Uppal
- Re: peer to peer messaging
- References:
- peer to peer messaging
- From: Bond
- Re: peer to peer messaging
- From: Thomas Weidenfeller
- Re: peer to peer messaging
- From: Bond
- Re: peer to peer messaging
- From: Guy Noir
- Re: peer to peer messaging
- From: Bond
- Re: peer to peer messaging
- From: Guy Noir
- peer to peer messaging
- Prev by Date: Re: Baffling class not found problem
- Next by Date: Re: Browser plug-in to interact with browser
- Previous by thread: Re: peer to peer messaging
- Next by thread: Re: peer to peer messaging
- Index(es):
Relevant Pages
|