You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/10/27 20:35:01 UTC
[PATCH] RemoteManagerHandler
Minor correction. The last patch set the default on the output stream to
not flush, but didn't catch that the login prompts needed to be flushed.
Looking through the various handlers, I'm not sure why we don't simply add a
flush to either the end of parseCommand or the loop that calls it, and only
put in explicit flushing were it is specifically desirable (such as emitting
a message right before an operation that could take a while).
The patch fixes a bug. The paragraph above can be deferred until after
release.
--- Noel
RE: [PATCH] RemoteManagerHandler
Posted by "Noel J. Bergman" <no...@devtech.com>.
Missed one!
-----Original Message-----
From: Noel J. Bergman [mailto:noel@devtech.com]
Sent: Sunday, October 27, 2002 14:35
To: James-Dev Mailing List
Subject: [PATCH] RemoteManagerHandler
Minor correction. The last patch set the default on the output stream to
not flush, but didn't catch that the login prompts needed to be flushed.
Looking through the various handlers, I'm not sure why we don't simply add a
flush to either the end of parseCommand or the loop that calls it, and only
put in explicit flushing were it is specifically desirable (such as emitting
a message right before an operation that could take a while).
The patch fixes a bug. The paragraph above can be deferred until after
release.
--- Noel