Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Refactoring/Remodelling/Renaming Call API

Hi Roland and All,

Although I don't have any objections to renaming things away from 'call API' for reasons Roland gives, won't 'telephony API' be confused with windows' 'TAPI'?  Some alternatives that occurred to me:


But I'm easy :)...if after further input from others Roland thinks that *.telephony.* API is best then we'll go with that.

Roland when you are ready to introduce the new plugins (whatever their names) please let me know and we'll coordinate on removing/adding to the build (and javadocs generation, etc).



Roland N. Fru wrote:



I started refactoring/remodelling the call API today and I would like to get your opinions with respect to an issue that has met some criticism from the community in the past.


The umbrella term “”Call API” seems inappropriate so I suggest we rename it to “Telephony API”. There are several reasons to support the renaming:


  1. “Call API” in certain contexts suggests some type of Invocation API which is clearly not the case with the ECF Call API.
  2. “Call” by definition limits the API capabilities solely to telephone CALLing although I can imagine the API handling other aspects within the telephony domain e.g. phone status, callcenter API, conferencing API etc. These are certainly not within the short term goals of the API, but the telephony namespace will “keep more doors open”.
  3. APIs similar to ours e.g. JTAPI, TAPI have traditionally carried the umbrella term “Telephony” and a design along the same lines will favor a suitable learning curve both for the users as well as for the implementers of the API.


I look forward to you dropping your thoughts on this. In case of positive feedback, I will rename the packages from “org.eclipse.ecf.*” to “org.eclipse.ecf.telephony.*”. e.g. the “” package will become the “” package.




_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx

Back to the top