In Fireplace Server, add the ability to accept a set of log entries to write as a batch. The batch is nothing more than just an array of discreet log entries. This can help reduce the chattiness of the API and lower the amount of HTTP traffic.
Libraries must be updated to add support for this. Essentially when initializing a logger a user must be able to specify they want batched logging and how big the batch is before transmitting.
Please note that the size of the batch isn't the only trigger to send logs to the server. Time should also be a factor. This ensures that batches that aren't full don't get stuck in limbo and never sent. For example, let's say you configure a batch size of 10, and the application hasn't logged anything in 20 minutes. At some point these logs should be shipped to the server (every 30 seconds, as an example).
In Fireplace Server, add the ability to accept a set of log entries to write as a batch. The batch is nothing more than just an array of discreet log entries. This can help reduce the chattiness of the API and lower the amount of HTTP traffic.
Libraries must be updated to add support for this. Essentially when initializing a logger a user must be able to specify they want batched logging and how big the batch is before transmitting.
Please note that the size of the batch isn't the only trigger to send logs to the server. Time should also be a factor. This ensures that batches that aren't full don't get stuck in limbo and never sent. For example, let's say you configure a batch size of 10, and the application hasn't logged anything in 20 minutes. At some point these logs should be shipped to the server (every 30 seconds, as an example).