Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

C Socket Programming

Name: Anonymous 2013-01-03 9:35

currently writing a client and a server program who exchange data via UDPv6/IPv6 and using ARQ with sequencenumbers and ACKs to ensure the data was send correctly
to do this you have to change the socket to O_NONBLOCK and then theres comes this tricky select()/pselect() function and I really cant get it to work
does some of you got an example for this problem?

Name: Anonymous 2013-01-03 9:36

>>1
The looney detector van, you mean.

Name: Anonymous 2013-01-03 9:38

select() is shit, use poll().

Name: Anonymous 2013-01-03 9:41

>>3
poll() is using way to much CPU time, select() seems far more intelligent as it looks when a socket-descriptor is ready to read/write

Name: Anonymous 2013-01-03 9:44

>>4
So does poll(). Are you high?

Name: Anonymous 2013-01-03 9:49

>>3
poll() is even worse as you must allocate an array of pollfd structures and it's even less portable than select()

Name: Anonymous 2013-01-03 10:03

>>6
It's less portable, but I don't see what's wrong with the pollfd structure.

Also, if you're programming for Windows, you're a faggot.

Name: Anonymous 2013-01-03 10:10

in the end nobody distributed a meaningful answer, like always
thanks for nothing

Name: Anonymous 2013-01-03 10:13

>>8
like always back to /g/ please

Name: Anonymous 2013-01-03 10:16

epoll, if you want something portable use c# LOL.

Name: Anonymous 2013-01-03 10:37

>>10
ROFL XD

Not funny.

Name: Anonymous 2013-01-03 10:53

>>8
It's because you're an asstarded fuckhead who uses this specific textboard to make serious questions.

Ask Stack Overflow, they will give you a serious answer (or probably ``downboat'' your question for a duplicate and not enough JavaShit).

Name: Anonymous 2013-01-03 13:01

>>11
It's funny because c# is portable whilst epoll is not. Not to mention that c#'s Begin and Async gives just as good performance compared to epoll...it's hilarious.

Name: Anonymous 2013-01-03 13:36

C# is shit. Microsoft is in the process of getting rid of .NET.

Just you wait, within this year, there will be a big shakeup over the failure of Windows 8. Ballmer the Jew will finally be ousted. They'll cut corners in an attempt to refocus their business on a new strategy.

Name: Anonymous 2013-01-03 13:39

http://www.i-programmer.info/professional-programmer/i-programmer/2830-was-net-all-a-mistake.html

It is time to reconsider the recent past and ask the question "was .NET just a forced detour on the road to another technology?"

Before anyone explodes I'd better say that I don't have a definitive answer to the question that the title raises - how could anyone have such an answer. However the recent unsettling behavior at Microsoft has caused me to re-evaluate my .NET experiences and think hard about where it all came from and where it is all going. It is interesting and I promise not to be too provocative just for the sake of it...

Name: Anonymous 2013-01-03 20:40

>>14
Win8 falling flat means that the Microsoft division that created .NET will gain influence over the Windows division. If anything, you should expect the .NET and Windows APIs to continue to converge toward the CLR way of doing things.

Name: Anonymous 2013-01-04 0:47

MS has 50 billion is cash. u know 8's no good when it is being shoved in your face, daily.

Name: Anonymous 2013-01-04 7:58

S Pocket Crogramming

Name: Anonymous 2013-01-04 16:08

recurse my anus

Don't change these.
Name: Email:
Entire Thread Thread List