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

WinSock w/ pthreads, C++

Name: Anonymous 2008-10-13 5:49

I'm testing a concept so excuse the messy code, it's my first time really using pthreads at all. Running into a bit of a problem; it handles the first client that connects just fine, but none afterward. At first I thought it had something to do with my accept socket, because if I closed the accept socket after setting it to the socket in my thread's object, it would close the connection, so I made an array of accept sockets. Still not working.

In short, I don't want bitching about my coding style, etcetera, as I just threw this together to see how it works. It's most certainly not going to be used in anything; it's just a learning tool of sorts. If anyone can find where and why it's not working as I intend it to, I'd greatly appreciate an explanation.

Code: http://pastebin.com/m47bff01e

Thanks.

Name: Anonymous 2008-10-25 16:53

>>36
No, exactly what you folks haven't been saying all along. The majority of what's been said was ridiculously vague or not concerning the problem at all. You've made it quite obvious that you're the one who's too stupid to read; your statement has no backing.

I was wrong in that it was my network code causing the problem, but that doesn't make everyone that said "LOLOL YOU SHOULD USE SOMETHING ELSE" or "LOLOL YOU SHOULD USE MORE C++ FUNCTIONS" or flat out didn't address the problem at all, right. Yes, someone finally said it was my broken network code - but that's too vague to be of much use. >>30 was the first to actually give me an idea of where things went wrong.

Note the following that either didn't help or were irrelevant:

>>2
>>3
>>4
>>5
>>6
>>7
>>8
>>9
>>10
>>11
>>12
>>13
>>15
>>16
>>17
>>18
>>19
>>20
>>21
>>22
>>23
>>25
>>27
>>29
>>31
>>32
>>34

and oh look >>36


So yeah... saying all along? Hardly.

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