|
Umm. Wait... WHAT? How does setting up a protocol so that it does something like MXP does, and sends a "Can you do <our protocol>", waits for a, "I can do <our protocol>", then, "Do <our protocol>", followed by, "Will do <our protocol>". Hard? Yes, standard telnet clients *won't* work right. Neither will those that don't support plugins for the new protocol, but nothing prevents you from releasing specs (Clear ones though please! We are still arguing with Zugg about why his client won't follow its own specifications correctly...) then letting someone else figure out how the heck to impliment it. You still get your custom client, since initially its all that would support it, but you don't have to bury your head in the sand and hope that someone doesn't duplicate it. And, depending on the interest, you might find yourself in the embarassing position MS did a number of times, where they announced, "We have this new protocol, which we don't expect anyone to 100% duplicate.", and the tech industry going, "Really!? Just a sec... Ah, here you go. We implimented this last week. Please point out which part of your protocol it doesn't support..."
I think you are involved with a lot of wishful thinking in this plan.
|