the socket classes that handle the data traffic in the Java API have a limit of 32KB per message. Normally this is more than sufficient for any application. Unfortunately there is no way from code to change these limits because they are set when the protocol encoder/decoder are created and can't be changed at runtime.
The only way is that we recompile one of the API libraries with a higher limit (let's say 128-256KB or so)
Another way around this is to understand why so much data is transferred in one shot and see if you can reduce it. Maybe this is a very long room list? Or a very large extension request? In the latter case you might switch to a more compact protocol such as JSON if you haven't already done it.
[EDIT] I may have misunderstood. Are you suggesting you could recompile the client library to support an increased buffer size? Is this a possibility? Perhaps you could let us override the default through a property passed to the JVM? We are planning on building a lot of games on SFS, and being able to load test them using the Java client API is really important for us.
java -jar <yourapp> -Dsfs.client.inDataMaxSize=64000 -Dsfs.client.outDataMaxSize=64000
Users browsing this forum: No registered users and 1 guest