On Mon, 28 Sep 1998, George wrote:
> >I don't think this will work -- what if there are two \n's in the
> >input stream, with no intervening \r? The client sends strictly in
> >Unix type file mode I believe -- never a \r. I could perhaps be
> >mistaken, though. So two blank lines get transmitted as "\n\n" which
> >causes the problem.
>
> It'll strip two \n's if there are two \n's. I'm not quite sure how the
> mudFTP client sends, but commenting out the above code doesn't work either.
> (infinite loop). Could create an exception for mudFTP in there.
mudFTP sends only \n - it's its own protocol after all.
You could skip it only once for mudFTP I suppose, in CON_FTP_DATA - I'll
try that when I get home from work today.
--
=============================================================================
<erwin@andreasen.com> Herlev, Denmark UNIX System Programmer
<URL:http://www.abandoned.org/drylock/> <*> (not speaking for) DDE
=============================================================================
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST