Opened 9 years ago

Closed 8 years ago

#370 closed defect (wontfix)

xfrin needs to be more asynchronous

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


For example, it shouldn't block on connect() so that it can react to shutdown event during a blocking connect(). Likewise, TCP send can also block, and it should be asynchronous for the same reason.

See also trac #216.


Change History (4)

comment:1 Changed 9 years ago by stephen

  • Milestone feature backlog item deleted

Milestone feature backlog item deleted

comment:2 Changed 8 years ago by shane

  • Defect Severity set to N/A
  • Milestone set to New Tasks
  • Sub-Project set to DNS

Possibly the design of xfrin needs to be revisited. We want an xfrin that can scale up to handling hundreds of thousands of zones, after all.

comment:3 Changed 8 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 8 years ago by jinmei

  • Resolution set to wontfix
  • Status changed from new to closed

canceling this ticket (opened by myself). we will switch to the new architecture
before trying to address this in the current implementation.

Note: See TracTickets for help on using tickets.