Add more formal enforcement on ByteBuffer size limitations.

[olegz]

While framework's main communication between client and Application Containers is achieved by exchanging ByteBuffers, some limitations around sanity must be enforced.
For example ByteBuffer already has some of it embedded by using Integer to allocate its size (thus limiting it by Integer.MAX_VALUE), but there has to be more at the framework level.
At the end of the day this is not deigned for pure echo-request-response type applications. Its about sending data for processing and receiving a reply about the status of the process.
One of those limitation could be:
Input: no more then 512Mb
Output: no more then 32MB
Its sounds reasonable at the moment and if there are use cases that would require these limits to be increased I would like to hear about them first, since as it happens more often then not the issue may be in the system architecture rather then frameworks capabilities/limitations.