by ECC on Fri Jul 30, 2010 2:15 pm
Yeah, that's the way it used to work in v2.1. But when we went to 8 processes there was too much data for the BCS to handle in a single file. We wanted separate config files for each process anyway, so that's the way that its structured.
Basically what was happening was that the browser would blast the configuration file at the BCS, and since its a small embedded device, it couldn't keep up and it start stalling data. By the time that it was ready to take the next round of data, the browser had already timed out.
The problem with a large config file may be solved in the future, although it turns out that it is a very complex problem.