Opened 9 years ago

Closed 9 years ago

#407 closed enhancement (duplicate)

Support for handling multiple requests concurrently

Reported by: zzchen_pku Owned by:
Priority: medium Milestone:
Component: xfrout Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Copied the comments from #299:

First of all, are we intentionally allowing multiple clients to connect to the xfrout server via the unix domain socket? The current implementation allows that because it inherits from ThreadingUnixStreamServer. This behavior might be good (e.g. if we use a multi-process model for b10-auth in the future, each sub process may want to make a separate connection to xfrout), but I'm not sure about the intent from the code. Actually, it rather seems to assume a single client.

Second, since the actual xfrout session works in the blocking mode, we cannot handle multiple xfrout sessions concurrently. This is not good if we have multiple large zones and when xfrout sessions run for these zones at the same time. And, of course, the shutdown procedure cannot (always) be as quick as it should be.

Depending on the answer to the first point, we might rather avoid using the socketserver framework. And, for the second part we need more sophisticated operation for xfrout sessions.


Change History (2)

comment:1 in reply to: ↑ description Changed 9 years ago by zzchen_pku

  • Component changed from Unclassified to xfrout
  • Type changed from defect to enhancement

For more details, please refer to #299

comment:2 Changed 9 years ago by zzchen_pku

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.