Royaltramp

I've written various programs in different languages, and have enough knowledge to easily learn anything further I need to know in: Java, Python, C++, VB6, VB.NET, C# and possibly Delphi. (I have never written in Delphi directly but I used to write scripts in a program whose language was based on Delphi). However, I've only ever written networked/socket based applications in VB6 before (client/server, messaging, etc), but that's due to the simplicity of the language and Winsock.

Now one of the things I've been interested in recently is networked or socket based applications. I have a basic text IRC client set up in Java, but that was written for me by a friend so I could see how little code was necessary for something like that.

My language of choice would probably be C++ or C. I have the least experience in those out of any language I've ever used, but I feel they're not much different from each other, or from other languages I've learnt, and it's worth it for the smaller compiled applications and less use of resources :P

So anyway, here's a few questions to make it easier to reply to the topic:

1) Can this be done without any additional software? I know with VB if you don't want to use Winsock you're forced to download new API functions that'll be automatically added to your application.
2) To anyone that has worked with sockets in C++ or C, what tips would you give, and where would you say would be the best place to learn from? (I'm not asking for source code here unless it's something basic, I prefer to learn through experience.)
3) Would it be easier to accomplish this in another language? (If so, what language would you recommend)
4) How would I go about accessing and writing to a MySQL database with C++ or C?

Thanks tons in advance.

-Matt

__________________

We Are Gr33n Machine

Spotswood

If it was me, I'd use C#. Otherwise, for C++/C checkout the Winsock Programmer's FAQ.

__________________
Rich
Custom Wooden Case Builder

Grandlo

"windows socket programming", it's an old book but was defacto standard socket reference for windows. everything it says is still relivant and it's well written.

http://www.amazon.com/Windows-Socket...5294935&sr=8-2