XPost: comp.os.linux.networking, comp.lang.misc, microsoft.publi   
   .development.device.drivers   
   XPost: comp.os.ms-windows.programmer.win32   
   From: cr88192@hotmail.com   
      
   "Joe Pfeiffer"  wrote in message   
   news:1bocq3alkt.fsf@snowball.wb.pfeifferfamily.net...   
   >S Claus  writes:   
   >   
   >> here is a question that probably does not have an easy answer.   
   >>   
   >> But I am curious about what happens when a new protocol is being   
   >> invented at some hardware manufacturer. How do the people who work on   
   >> these actually go about inventing a new protocol?   
   >>   
   >> What steps do they go through?   
   >>   
   >> Any good books / websites that deal with this subject? (preferably   
   >> books)   
   >   
   > More than no easy answer, it doesn't even have a unique answer.  When   
   > you write a client/server application, you will develop a new protocol,   
   > which may be as simple as "send me a packet with a sensor number, and   
   > I'll answer with a packet with a sensor setting", or may be a particular   
   > AJAX request/response pair.   
   >   
   > It's really the same as how anything is developed:  you figure out what   
   > the requirements are, and you meet them.  What's involved in doing that   
   > is entirely situation-dependant.   
      
      
   we all know that all other options are meaningless when compared against the   
   incredible greatness of SOAP...   
      
   after all, SOAP is the one true protocol and is necessarily implemented,   
   even if it just so happens that both ends are incompatible due to being   
   implemented using different versions of the schema, this is merely an   
   "implementation detail" (in much the same way as that it is such low-level   
   details that software runs on computers, or that humans need food and air to   
   survive...).   
      
   (and in a condescending voice) the truely intellectual would not concern   
   themselves with such low-level details, and instead focus on the "bigger   
   picture", a world where software is not constrained to running on computers,   
   and humans can propel themselves into space and explore alien worlds via   
   little more than the immense powers of their own flatulence...   
      
   nevermind the ignorant masses and all their naysayers...   
      
   ok, not really, just a sort of an unrelated semi-rant in the above...   
      
      
   but, yes, how one will design a protocol, ... will depend highly on the type   
   of system being implemented, operating requirements, ...   
      
   so, it is not so much about any one-true-strategy, but the careful   
   consideration and weighting of the various factors involved (much as in many   
   complex systems). and, often, it may well make sense to allow the use of   
   multiple "competing" possibilities, serving as such to allow some level of   
   experimentation and weeding out options which do not work as well as ideal.   
      
   so, rather than pursue the ideal of genericness, one can pursue the ideal of   
   openness...   
      
      
   > --   
   > As we enjoy great advantages from the inventions of others, we should   
   > be glad of an opportunity to serve others by any invention of ours;   
   > and this we should do freely and generously. (Benjamin Franklin)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)