This have really gotten interesting on the data base back end of the application. With the database being itself at a remote location, web services was the natural answer to the “How am I going to get my data over there?” question.
To no surprise of my own, the maximum size of a SOAP message that may be passed is 4 megs by default in the machine.config spec file for my .NET 1.1 framework I'm working with. Personally I don't see why any of this should change in 2.0 when folks (like myself can just override that specification in their own web.config specification file for what ever their application needs to do.)
Just for yucks, I'm increasing the default to 256 megs and seeing how much hang time I can get while passing the HUGE objects generated by the Puzzler's output.
<httpRuntime executionTimeout="180" maxRequestLength="262144" minFreeThreads="26" minLocalRequestFreeThreads="13" />
Notice how the minimum number of free local threads was also increased from 8 to 13 for solving all 26 directional possibilities of the puzzle (One thread cover one bi-directional possibility within the puzzle).