#3220: Submitting a ticket is very slow
-----------------------------------------------------+----------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: ticket system | Version: 0.9.5
Severity: normal | Resolution:
Keywords: submit ticket changes slow notification |
-----------------------------------------------------+----------------------
Comment (by eblot):
> ''Why not address the problem by making the notification asynchronous?''
I would say "keep it simple". Or "keep keeping it simple" ;-)
Introducing background tasks in Trac seems to be quite overkill, and would
probably lead to create a new bunch of hard-to-solve issues, to fix up the
issue at the wrong place (in Trac, rather than at the MTA level).
I don't see the point to introduce serialization in email notifications,
whereas the MTAs are already able to receive concurrent notifications.
Trac is not a MTA debugging agent. To detect long latency issues, it's far
easier (and safer...) to retrieve the time before the SMTP connection and
after the notification, and log a warning message when the time difference
reaches an upper limit.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3220>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
