Messages generally look similar to the following example: MSG 1 0. Instead, the payloads exchanged on the application channels consist of three-letter major command codes, mostly followed by three-letter minor command codes, often followed by bencoded data. The authors of SubEthaEdit decided to ignore the recommendation of the RFC authors to use MIME. Each channel has an associated profile, identified by an URI, that defines the protocol for messages exchanged on that channel. Messages in the special channel 0 are fully specified in RFC 3080, all other channels are freely usable by application protocols. The BEEP protocol manages multiple virtual channels for independent data streams over a single connection. (Very simple versions of both in case of the SubEthaEdit protocol – the only MIME header used is Content-Type.) The actual conversations between SubEthaEdit client and server are done on top of the BlocksExtensibleExchangeProtocol ( RFC 3080 and RFC 3081), which is a generic, channel multiplexed, transport protocol that uses XML and MIME. (The default port is 6942, which codingmonkeys says can be remembered because 6*9=42 – it’s a Hitchhiker's Guide to I have no particular interest in supporting this part of the protocol: sessions will be initiated by giving the hostname or IP and optionally port. In any case, it simply advertises with no additional data that I can see. While this is true, its use of Bonjour isn’t interesting it’s only useful when you have multiple users on the same subnet. You’ve probably heard that it uses Bonjour (AKA ZeroConf, Rendezvous). The SubEthaEdit protocol has a fair number of parts. #Subethaedit 5 licenseHow does the MIT License change these? Introduction The reverse engineering requirements were written when SubEthaEdit was proprietary. SubEthaEdit became MIT licensed in October 2018. I figure that if Andrew Tridgel feels OK saying in open court that he did these things against Microsoft, we’re probably safe from the presumably less litigious codingmonkeys. While it is my belief that reverse engineering for the purpose of interoperability is a protected right, it’s not 100% clear, esp as you go from jurisdiction to jurisdiction. What’s in is information gleaned by any of the methods described in - specifically, anything that only involves running the program, and examining the information it sends across the wire. This means that information gleaned from examination of the binary you got from is right out, including simply running strings on it. This information can then be used to interface other editors with SubEthaEdit, for example Emacs.įor projects working on interfacing Emacs and SubEthaEdit see:īefore getting on to the meat of this page: Please do not add any information of questionable source. The purpose of this page is to describe the protocol used by the SubEthaEdit collaborative editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |