> From: David kerber [mailto:dcker...@verizon.net] > A typical client will have 2 to 5 items to send per > transaction (they're > actually lines from a data logger's data file), and each line > is done in > a separate POST request. The frequency of transactions varies widely, > but typically won't exceed one every 10 or 15 seconds from any given > site. As I mentioned earlier, each data line is small, 20 to > 50 bytes.
OK, so your top end is about 1 line every 2 seconds. You'll need at least 2 round-trip times (RTT) per line (SYN out, SYN-ACK back, ACK-DATA out, ACK-DATA back, plus the FIN-ACK out), but that's not a high rate. > We had looked at batching up the transmissions before, and > it's still an > option. However that adds a bit of complexity to the software on both > ends, though the gain would be far fewer individual requests to > process. For now, we prefer the simplicity of line-by-line > transmission, but if we start running into network limitations we'll > probably start batching them up. I'm interested - and this is now a long way from Tomcat, hence the [OT] mark above. If a set of lines represents one transaction, why would you ever not send it and try to process it atomically? Or is it acceptable to have part-transactions within your system? - Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org