unity-src
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Unity-irc3] Binary? Ascii?


From: Andreas Bierfert
Subject: Re: [Unity-irc3] Binary? Ascii?
Date: Tue, 22 Apr 2003 11:09:24 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030416 Thunderbird/0.1a

Hi,

wow 8 subscribers, does that mean I have to check my mails for content now ?? ;) Anyway I myself really like doing stuff with telnet but as for the rest I tend to support the pro points on the binary side. As long as jast writes the documentation for it I'm happy j/k

My promised cvs document will be online soon, I guess I will go over it with jast today at university, get the writing errors out and TeX it a little and then upload it to the official cvs ...

Best regards

Andreas

Jan Krueger wrote:

Greetings,

first of all, I'm delighted that we have that many members now. ;) A look at
the stats shows 8 subscribed list members right now -- that's a new record.
Impressive. Keep going.

Back to topic, anyway. We've talked this over already (on IRC, I think) but
haven't come to any conclusion. Today's question is -- binary protocol or
text-based protocol?

Pro binary:
- less traffic
- easier to parse
- less buffer overflows in the implementation (at least I guess so)

Pro text:
- more flexible
- easier to debug (telnet client can be used)

I'd say we'd focus on a binary protocol and also add a loosely IRC-compatible
protocol for debugging and compatibility reasons.
Either way, we'll have to write some kind of excellent documentation. I'll
take care of that since I still haven't told you all of my ideas (sigh).
Anyway, I do know the way of the TeX now so that won't be too hard for me.

------------------------------------------------------------------------

_______________________________________________
irc3 (Unity) public discussion mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/unity-irc3







reply via email to

[Prev in Thread] Current Thread [Next in Thread]