Search:

Oi. This is embarassing, the problem [seems] to be resolved. By some bizzare twist of logic the code I had written was *ahem* poorly interacting with other code I wrote, causing the socket to open...

Sorry, I should have made it clear that I am not null terminating the string; I don't think recv() would write past the 1024 limit I specified? I do not have much experience with Sockets; The rest of...

I am telling the socket that no more data is to be written to it.
shutdown Function (Windows)


One's a fixed array 1024, the other is a char* pointer of variable length depending on the length...

Hey there,
I've had this problem for a little bit, and it is now time to track it down, as its become obscenely troublesome.

Premise:
I am using sockets under WinSock2 to retrieve an XML page...

Resolved. (and I've bookmarked that FAQ) Thanks guys.

I'm self-teaching Templates, and I think I've gotten a grasp on the concept (doesn't seem too, too tricky) but the problem lies when I try to compile, I'm trying this, that and the other thing, and...

Just a shift in memory? Seems simple enough :)

Thanks guys.

Resolved, thanks. -- Still curious though, why would the printf(""); make it work?

I've been slowly teaching myself C++ and haven't gotten around to the String class just yet. I'm working under Vista Business (laugh if you must) and Visual Studio 2005 (again).

When attempting to...

after I finish reading the fifo... does it clear itself? or am I looking at a whole new set of problems trying to read from this thing on a continous basis?

Edit:
I've been unconditionally...

not in one read cycle...

read_fifo opens and closes it once during it's run, but after it's read, the fifo is closed, the data is preserved, processed and the system starts again... it's running...

my read statements no longer read from the pipe correctly, client returns a Broken Pipe error, and the server returns a (null) string...

I'm investigating myself, but it's no longer blocking.
...

I'd be less irritated if I didn't really need this, but it's still blocking, I've changed the code to the following (for the read_fifo)




FIFO_DATA *read_fifo( char filename[256] )
{
...

I'm using the functions in this order (example with limited details to prevent confusion)


main ( )
{
initalize_fifo( )
for ( ;; )
{
handle_fifo( );
}

Greetings,
Simple issue, but my own research has turned up nothing.

I'm attempting to create an intra-process communication system to create a communication & control program for a server daemon...