removing the length limit on strings

[julochrobak]

There is a maximum length, MAX_STRING (defined in config.h file, currently at value of 1024), restriction on all string values. The string data type should not put any constraints on the length of the values.

This task is to completely remove the MAX_STRING restriction from the string data type. In order to do that, the chunked encoding of HTTP response from bandicoot could cut a tuple in the middle of a string attribute.

[ostap]

here are my review comments:

1. looks like splitting the data on MAX_BLOCK boundaries introduces a lot of clutter. can we avoid it? the values are anyways loaded into the memory.
2. trailing white spaces

[julochrobak]

1. the MAX_BLOCK is unfortunately coming as a requirement from other piece of the code 'sys_proxy'. The data sent by the processor to the main process must be at most of the MAX_BLOCK size. I did not manage to come up with a simpler solution without rewriting the sys_proxy part.
2. I removed the trailing spaces.
3. I added one more FIXME into the bandicoot.c, there seems to be a memory leak on the tuples of the return if a client closes the connection before all the tuples were sent to the client. This now is applicable to the 'PBuf' instance as well.
4. There is one more use case of the MAX_STRING which I did not get rid of. The string literals in the language must be at most MAX_STRING characters long.