Board Thread:Support Requests - Getting Technical/@comment-1504358-20121227231305/@comment-1504358-20121230154605

Because the feature should be available? Why would I have to chunk the request if I can avoid it?

It's like if you buy a TV then realize back at home that the remote control does not work properly, and you call the store clerk to complain about it and he/she replies "Well, boss, there are buttons on your TV to control it, just use it, isn't that obvious?"

There is a bug here, and IF they can't fix it, I'll have to unhappily chunk my requests, but until they get back to me, I'll wait and see. If the server can't handle that much data in a single request, an error should be sent back.

Chunking the request would look less pretty than the not-chunked version (in the logs, 2+ updates for a page update instead of only 1), multiplied error handling for the bot, more complex algorithm for the updates (e.g. first update is "text" then it's "appendtext"). Then there is stuff related to the server: what's the max data threshold? Is it a hard limit (always the same size) or is it a soft limit (it depends on the server load)? Sending in chunked data would also mean more requests to the server.

Anyways, I guess you see my point. I'd like to avoid chunking if I can.