My client app is working so far. On my own server is running a tcp script which listen on a special port. The script received the messages from the client and saves the data to the database.
But the problem is that only every 30s comes a message. It doesn't matter what frequency setting is set in the client app.
The client app shows every 30s an error (Übertragung fehlerhaft) while sending - but my server received the messages.
It seems that the app opens every 30s a new connection (new client port on server site). But my server script would wait for other messages on the old port.
Should the server answer to the client after receiving a package? Why does the app "think" that the transmission failed? What does the app needs for no error message?
thanks a lot, Manuel
You have to comply with HTTP protocol, not just pure TCP. Which means that you do have to send a response.
Ok, thanks.
I find out, if the server answer with:
HTTP/1.1 200 OK\r\n\content-length: 0\r\n\\r\n\
All works find.
My client app is working so far. On my own server is running a tcp script which listen on a special port. The script received the messages from the client and saves the data to the database.
But the problem is that only every 30s comes a message. It doesn't matter what frequency setting is set in the client app.
The client app shows every 30s an error (Übertragung fehlerhaft) while sending - but my server received the messages.
It seems that the app opens every 30s a new connection (new client port on server site). But my server script would wait for other messages on the old port.
Should the server answer to the client after receiving a package? Why does the app "think" that the transmission failed? What does the app needs for no error message?
thanks a lot, Manuel