Updated: 4/2/02; 9:05:15 AM. |
dizzyd daily, dizzified jabberish Tom Lord's Decentralized Revision Control System [Slashdot]
A cool new version control system...I'm looking forward to trying this one out.
4:18:33 PM Finally, I don't like the fact that BEEP base-64 encodes SASL data and sticks it into a XML tag during the auth sequence. I understand the need for structuring data in the exchange, but the whole point of a framing protocol is to allow the exchange of abitrary chunks of any type of data -- including binary. 9:59:03 AM
Another BEEP issue that bugs me is the idea that you can only authenticate once for any given session/channel. This could be problematic for some of the stuff which Jabber consumers will need in the future. 9:52:17 AM
More research on the BEEP front. I've completed an indepth analysis of the core spec. Overall, it's ok. One section that particularly bugs me is 2.3.1.2...check out the way that they embed XML within XML as CDATA. This approach is wrong on so many levels -- namespaces are the way to go here to solve this problem. 9:49:33 AM
|
|