46
[x86] Announcements / Re: A new member! Yeah!
« on: October 12, 2009, 06:46:23 am »
Welcome to the brotherhood. Cookies to the left.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Lol. Or maybe.. I was just using a bot to play around with the sockets
Dun dun dun
Refusing for the last couple years to learn how the .Net platform works, I've decided that I probably should knock this one off my shoulder. Actually, it wasn't until 3 days ago when my dad's friend asked if I could write him some new server software for his company... The software will be accepting / responding to many multiple active connections.
So I did some research and asking around and noticed a lot of people pointed me towards .Net. I would do it in C, but my experience level isn't quite there yet and I know if I did something like that with my level of experience, I would create clusters of memory leaks.
Knowing VB6, I thought it would probably be easiest to go to VB.Net. Therefore, I would be able to get the project done a lot faster.
So my questions are...
Would .Net be suitable for this project?
Is C# and VB equivalent in performance since they both compile down to the same CLR?
As long as using the TcpListener class doesn't hinder performance (nothing major), then it wouldn't be a problem.
The documentation's I've read create a new thread per connection... wouldn't that greatly decrease performance if say.. you have a 400 connections?
For exampleCode: [Select]Public Sub InitNewClient(ByVal Socket As TcpClient, ByVal clientIPAddress As IPEndPoint)
clientSocket = Socket
clientIP = clientIPAddress
printf("Incoming client " & clientIP.ToString.Split(":")(0), _SOCKET)
Dim clientThread As Threading.Thread = New Threading.Thread(AddressOf ClientDataArrival)
clientThread .Start()
End Sub
The subroutine ClientDataArrival is obviously just a loop that constantly checks the stream.
.NET is great if you're wanting to develop windows applications. If you want more breadth than that, then you'll obviously want to consider other platforms?
I'd recommend doing yourself a favor and ignoring your attraction to VB. While, to my knowledge, VB.NET is everything but superficially equivalent to C#, learning C# syntax will bring you that much closer to being familiar with all of the other languages that smell like Java, which is a definite advantage.
Plus, VB is ugly and hard to read.
.NET is a great platform for network applications.
No, quit being lazy.
Wouldn't you rather find somebody you get along and can hang out with, and ALSO have sex with?I think that's pretty obvious: sex.
(Maybe that's a stupid question )
You planning on using a Warden BNLS server to handle requests? -- As far as I know implementation of 0x05 can't be done
Negative.