Bug #45571 Agent doesn't have configurable response size

Description:
There are cases (with large inventories) where a customer might want to use a larger response size with the agent. Currently it's hard-coded to 65K.

How to repeat:
N/A

revno: 1360
revision-id: mark@mysql.com-20090617210318-nz7v2953pg82889g
parent: merlin@dl380-g5-a.mysql.com-20090615180602-z55tf14xv5vel7n8
committer: mark@mysql.com
branch nick: trunk
timestamp: Wed 2009-06-17 16:03:18 -0500
message:
  Added agent option --agent-max-response-size which will set the maximum size (in bytes) of the response the ag
ent will send to the service manager. The default is 65536.

Patch installed in versions => 2.1.0.1063.

Verified. This option has been added to 2.1.0.1067

On the logs you see something like this when setting the size to 50000 bytes

(message) --> sending heartbeat (293 bytes) (shutdown = 0)
(message) --> sending heartbeat (52331 bytes) (shutdown = 0)
(message) --> sending heartbeat (52416 bytes) (shutdown = 0)
(message) --> sending heartbeat (52143 bytes) (shutdown = 0)
(message) --> sending heartbeat (9590 bytes) (shutdown = 0)
(message) --> sending heartbeat (293 bytes) (shutdown = 0)

note that the first list instances heartbeat will be larger than the value specified on the ini file.

A change entry has been added to the 2.1.0 changelog:

The Agent did not have a configurable response size.

The response size was hard coded to 65K. However, with large inventories, the customer might need to use a larger response size.