... | ... | @@ -678,13 +678,13 @@ The work breaks down into two parallel tracks: Query fulfillment and LeaseQueryL |
|
|
2.1 Create the initial class hierarchy from CmdHttpListener hierarchy
|
|
|
a. HttpThreadPool -> IoServiceThreadPool, this class could probably be in asiolink, there
|
|
|
really is nothing in it that is HTTP or even TCP specific. It's really a pool of IOService
|
|
|
driven threads.
|
|
|
driven threads. - #2581
|
|
|
b. HttpListener* -> TcpListener*, these classes could reside in asiolink and possibly also be used
|
|
|
as base classes for Http code, though this would be ancillary to making BLQ work.
|
|
|
c. Derive LeaseQueryConnection from TcpConnection
|
|
|
d. CmdHttpListener -> LeaseQueryListener, self explanatory
|
|
|
as base classes for Http code, though this would be ancillary to making BLQ work. - #2583
|
|
|
c. Derive LeaseQueryConnection from TcpConnection - #2639
|
|
|
d. CmdHttpListener -> LeaseQueryListener, self explanatory - #2635 created MtTcpListenerMgr from CmdHttpListener. LeaseQueryListener will derive from (or perhaps be an instance of) this class.
|
|
|
|
|
|
2.2 Implement LeaseQueryConnection packet read and write logic (i.e. replace Transaction logic)
|
|
|
2.2 Implement LeaseQueryConnection packet read and write logic (i.e. replace Transaction logic) - #2639
|
|
|
2.3 Implement BulkLeaseQuery, XidQuery, XidResponse classes
|
|
|
2.4 Implement query queueing and QueryWorker, QueryWorker management
|
|
|
2.5 Utilize LeaseMgr BLQ interface to fetch results and build responses
|
... | ... | |