replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects) #3

christian-schwarzbauer · 2017-11-05T07:30:13Z

right now a new HTTPClient object is created for each Beacon.send() call. given that usually the number of different server IDs is very limited (~3) and the monitor name is hardly ever changed, I suggest e.g. pooling of the HTTPClient objects.

…-value-base-object to master * commit '87d1304680c7da111363c125e04ee8019a4c28f6': Minor styling fix found in the review Implement the base class representing a JSON value GitOrigin-RevId: 2a7fd081b34846da0e9c52ad492acf4a3134d634

christian-schwarzbauer added the enhancement label Nov 5, 2017

christian-schwarzbauer assigned stefaneberl and thomasgrassauer Nov 5, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects) #3

replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects) #3

christian-schwarzbauer commented Nov 5, 2017

replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects) #3

replace creation of new HTTPClient objects for each Beacon.send() (e.g. by pooling HTTPClient objects) #3

Comments

christian-schwarzbauer commented Nov 5, 2017