Home > slashdot > Naming Bi-Directional Streams In an API?

Naming Bi-Directional Streams In an API?

January 29th, 2011 01:08 admin Leave a comment Go to comments


DingoTango writes “My coworker and I are designing an infrastructure API to manage data streams. It will allow a client developer to set up streams going to and from some invoked server functionality, and allow a server developer to write services that both consume and produce streaming data. Our quite civil disagreement involves naming: From the perspective of the client platform, the client’s output stream goes to the server, and input stream comes from it. For the purpose of any ensuing discussion, let’s call this the ‘Local’ perspective. However, if the client developer considers the service to be a widget, then the stream going to the service is the input stream and the stream coming from it is the output. Let’s call this the ‘Widget’ perspective. As this is an infrastructure utility, we aren’t able to name the streams according to function. What say ye, Slashdot? Is there any precedence, experience, or ungrounded yet vociferous opinion that will resolve this for us?”

Source: Naming Bi-Directional Streams In an API?

Related Articles:

  1. Naming and Shaming ‘Bad’ ISPs
  2. Naming All Lifeforms On Earth With Hash Functions
  3. Experiments In Realtime News: The Eqentia Streams
  4. Do Twitter’s New Application Naming Rules Spell Bad News For TweetDeck?
  5. Twitter To Add Places And User Streams
blog comments powered by Disqus