Comments on: i p freely

By: Darkhorse

Darkhorse — Sat, 17 Dec 2005 15:34:25 +0000

The reason they want you to know COBOL is because there are TONS of legacy apps waiting to be migrated to alternative technology right now…

By: Chris

Chris — Tue, 13 Dec 2005 02:19:02 +0000

Depending on your application's goals, you'd need to create server and client components for your project. System.Net.Sockets has everything that you need. If both NAT routers have the same holes poked in them, let's say TCP 6299, then your server and client and components should do all communication over that port: server.cs


// start the server
TcpListener objSrvr = new TcpListener(6299);
objSrvr.Start();

client.cs


// connect to the server
try
{
    // use IP of the server computer here instead of localhost
    TcpClient objClnt = new TcpClient("127.0.0.1", 6299);
}
catch
{
    Console.WriteLine("Connection failed");
}

If the ports aren't known beforehand, I suppose you could always have the client send a special hash to a range of ports that only the indended server will repspond to. So when the client gets the expected response, it should store which port it was on - esentially, an ad-hoc port scanner.

By: Carmen

Carmen — Tue, 13 Dec 2005 01:24:46 +0000

Any idea how you could create a socket connection between two computers behind NATs in C#???

Carmen

By: scorpion53061

scorpion53061 — Thu, 08 Dec 2005 16:05:31 +0000

COBOL. I never thought I would have to learn this. It was suppose to have died. Every where I go though they want hteir programmers to know this language.

By: Chris

Chris — Thu, 08 Dec 2005 15:53:17 +0000

Not at all. Well, maybe the COBOL class will be a tad crazy

By: scorpion53061

scorpion53061 — Thu, 08 Dec 2005 15:48:23 +0000

well it is huge.

I am starting school next semester. I enrolled in Java, C++ and COBOL. Do you think i am crazy?