Transfer Encoding Chunked. This directive is used to send the series of data in a chunk format but have to mentioned the length of each chunk before sending the chunk of the data in hexadecimal format like rn and then the chunk itself. So it seems clear for me client to server communication can be chunked.
In cte each chunk is preceded by its size in bytes. Chunked there is no content length specified the server tells us it will send a bunch of chunks whenever it has data and. Chunked there is no content length specified the server tells us it will send a bunch of chunks whenever it has data and when the response is done it will tell us by closing the connection.
A zero size chunk indicates the end of the response message.
Chunked encoding is useful when larger amounts of data are sent to the client and the total size of the response may not be known until the request has been fully processed. We cannot change the encoding on the response that is sent from a talkback but you can use a thingspeak channel as a proxy for talkback. Reading rfc 2616 section 36 states that the server must send a 501 response when receiving a transfer encoding header it does not understand. The j2me httpconnection which comes with midp lets you make http requests to your server.