using network communication in .NET

T

Tony

Hello!

This is the scenarion that we want to implement.
We have a computer called A which register itself on a superviser server
about it's existence so other
computer can get the identification about computer A.

Now computer B wants to communicate with computer A so computer B ask the
superviser server about the identification for
computer A so B can start communicate with computer A.

Now to my question what kind of identification is just when computer A
register itself on the superviser server so other can get this
identification
for computer A. Have you some understandable example about how to do this.
What classes are relevant in this case?

//Tony
 
C

christery

Hello!

This is the scenarion that we want to implement.
We have a computer called A which register itself on a superviser server
and so on...


Got an idea what to look into...

Look at ebXML or WS/UDDI examples.

A SOA solution like NIM based on OpenSys using CORBA is another but
then u get into the Java/JNI swamp before going .NET again.

A glance at LDAP or M$ AD solutions as a reposytory might be worth
googling about.

Havent looked into RPC/COM+ and reposytorys.

There might be something abaout that A<--->B in (some) OPC solutions
but they normally integrates different PLC-systems with SCADA products
by configuration, not by autorecognition.

There is always those ESB solutions but they tend to adress (a bit)
larger systems, maybe there is a nice project going on att
sourceforege about that.

M$ wants u to run msmq and a BizTalk for orcestration if sync/async is
demanded for a PDA...

Connect all computers to a DB and use that as a communication link.

Multicast might be another approach, there shoukd be lots of examples
for audio/video streaming using multicast.
Now to my question what kind of identification is just when computer A
register itself on the superviser server so other can get this
identification


Or are u just asking for wins/dns? to replace those (LM)HOST files <g>

//CY
 
T

Tony

Hello!

If it's possible we intend to use some kind of remote communication between
computer A and computer B when B has got the identification for computer A.

//Tony
¨
 
C

christery

C

christery

Other solutions involve manual configuration of routers, proxies, or  
firewalls to allow some specific address to work for computer B to contact 
computer A, to try to trick the router, proxy, or firewall into passing  
communicates using a technique known as "hole punching" (UDP hole punching 
can be reasonably reliable, but TCP is much more iffy), or if dealing with 
a NAT router specifically, one might use Universal Plug and Play ("UPnP")  
to retrieve an address that's usable by computer B to contact computer A.
Aha, just missed what he was asking about.... why didn´t I think
UPnP...

//CY
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top