Re: Messenger-Esque Windows Service: How Do Major Messengers Do It?
- From: Alex <nielsena54@xxxxxxxxx>
- Date: Thu, 14 Jun 2007 17:48:42 -0000
On Jun 14, 8:03 am, "Jeff Hopper" <j...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
plz> wrote:
How about something like this?http://www.eggheadcafe.com/articles/20020323.asp
Jeff,
This is very close to what I am envisioning. However, the IP address
of the tcpListener is known in this case. As I've done some research,
I can better state my needs:
1) A centrally located client will listen for a successful
connection / login from a desktop client or windows service on a
user's computer.
2) Once the login is successful, the central client needs to be able
to send requests to the desktop client for database information,
almost like a web service.
My major hangup is: How does the central client know what address to
send requests to? For example, a request sent to my external ip
address right now will hit my router, not my computer.
A followup question: Since the article you pointed out shows how to
respond once a connection is made, would it make sense to maintain a
persistent connection?
That article was a great step. Thank you very much for pointing me to
it.
-- Alex
.
- References:
- Prev by Date: Re: Problem after installing some windows updates (935839,929123,935840)
- Next by Date: Re: Framework runtime environment
- Previous by thread: Re: Messenger-Esque Windows Service: How Do Major Messengers Do It?
- Next by thread: Re: Messenger-Esque Windows Service: How Do Major Messengers Do It?
- Index(es):
Relevant Pages
|
