Well, I'm not doing anything related to the http protocol. We are supposed to create our own application layer protocol to handle the messages. The messages sent from client to server is just raw text.
I think what I'm really asking for is if ACK is a special message (with a specified format)? Of course I can make some formatting to my messages and then define an ACK-message, but that's all about what I do with the data being sent.
So is ACK a special type of message with a defined format?
In that case, "ACK" is just conceptual* (and the "concept" is pretty self-evident methinks -- you have pretty much explained it yourself). As Zuk points out, you could use anything as the actual signal. When I do client server stuff, I like to use single byte signals (255 is enough...), usually capital letters. So "A" could mean "acknowledged".Originally Posted by daghenningsorbo
On the other hand, since an ACK will not have any further content, you could make it more elaborate to prevent confusion:
* the literal "ACK" is from http & the SYN-ACK "handshake" used by web servers.Code:#define ACK "<!Recieved!>"
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Thank you for your answer. That cleared things up for me.
