[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ecf-dev] AW: ecf-dev Digest, Vol 21, Issue 2
|
Hi all,
Just a point of precision in reaction to Scott's mail. My suggestion is to
rename it to "ECF Telephony API" in analogy to the existing "Microsoft
Telephony API - TAPI", "Java Telephony API - JTAPI", "Cisco Telephony API"
etc.
Greetz,
Roland.
-----Ursprüngliche Nachricht-----
Von: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx] Im
Auftrag von ecf-dev-request@xxxxxxxxxxx
Gesendet: 02 April 2007 00:35
An: ecf-dev@xxxxxxxxxxx
Betreff: ecf-dev Digest, Vol 21, Issue 2
Send ecf-dev mailing list submissions to
ecf-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
or, via email, send a message with subject or body 'help' to
ecf-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
ecf-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ecf-dev digest..."
Today's Topics:
1. Re: Refactoring/Remodelling/Renaming Call API (Scott Lewis)
2. Re: Refactoring/Remodelling/Renaming Call API
(Pierre Henry Perret)
3. smack 3.0.0 availability: please respond if working on voip
(Scott Lewis)
4. Re: smack 3.0.0 availability: please respond if working on
voip (Scott Lewis)
5. Re: Refactoring/Remodelling/Renaming Call API (Chris Aniszczyk)
----------------------------------------------------------------------
Message: 1
Date: Sun, 01 Apr 2007 08:59:58 -0800
From: Scott Lewis <slewis@xxxxxxxxxxxxx>
Subject: Re: [ecf-dev] Refactoring/Remodelling/Renaming Call API
To: "Eclipse Communication Framework (ECF) developer mailing list."
<ecf-dev@xxxxxxxxxxx>
Message-ID: <460FE50E.1070704@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
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:
*.voip.*
*.phone.*
*.telephone.*
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).
Thanks,
Scott
Roland N. Fru wrote:
>
> Hi,
>
>
>
> 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 "org.eclipse.ecf.call
>
<http://www.eclipse.org/ecf/org.eclipse.ecf.docs/api/org/eclipse/ecf/call/pa
ckage-frame.html>"
> package will become the "org.eclipse.ecf.telephony.call
>
<http://www.eclipse.org/ecf/org.eclipse.ecf.docs/api/org/eclipse/ecf/call/pa
ckage-frame.html>"
> package.
>
>
>
> Regards,
>
> Roland.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/cc7a94
e9/attachment.html
------------------------------
Message: 2
Date: Sun, 1 Apr 2007 18:54:24 +0200
From: "Pierre Henry Perret" <phperret@xxxxxxxxxxxxxxx>
Subject: Re: [ecf-dev] Refactoring/Remodelling/Renaming Call API
To: "Eclipse Communication Framework (ECF) developer mailing list."
<ecf-dev@xxxxxxxxxxx>
Message-ID:
<ed41b54d0704010954r16b896fga666987ef6cd2983@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
+1
--
Pierre-Henry
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/73a748
87/attachment.html
------------------------------
Message: 3
Date: Sun, 01 Apr 2007 13:46:07 -0800
From: Scott Lewis <slewis@xxxxxxxxxxxxx>
Subject: [ecf-dev] smack 3.0.0 availability: please respond if working
on voip
To: "Eclipse Communication Framework (ECF) developer mailing list."
<ecf-dev@xxxxxxxxxxx>, Moritz Post <moritzpost@xxxxxx>, "Roland N.
Fru" <roland@xxxxxxxxxxxxxx>, Pierre Henry Perret
<phperret@xxxxxxxxx>
Message-ID: <4610281F.4070507@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Hi Folks,
FYI, Smack version 3.0.0 is now out and available here:
Libs: http://www.igniterealtime.org/downloads/index.jsp#smack
Source: http://www.igniterealtime.org/downloads/source.jsp
For those current working on Jingle support in ECF call API, this
release has Jingle support in it.
I've created a plugin from both the smack 3.0.0 API with the jingle
extension API and made them available via the ecf1.osuosl.org site for
all of us to use. See the attached project file to import this project
into your workspace. Note for the time being I've given the plugin the
id 'org.jivesoftware.smack3' to distinguish it from our current plugin
'org.jivesoftware.smack'. Note also that Smack 3.0.0 requires JRE 1.5.
I suggest that we coordinate our efforts on the use of smack 3.0.0 to
introduce Jingle support into ECF (and extend the call API as needed to
do so). I think committer Roland Fru (roland@xxxxxxxxxxxxxx) and I
should jointly lead this work...i.e. on the call API, use of Smack 3.0.0
for Jingle support, work on other providers (e.g. skype, sip, etc), and
work on UI's and/or applications.
I would like to have a conference call this coming week (April 3) about
coordinating work among all of the interested folks. Could people that
are interested in participating in this effort (e.g. Roland, Moritz,
Pierre, myself, any others) please indicate when during the week
(day/time) would work for a 1 hour conference call by responding to the
ecf-dev mailing list? I'll arrange for the conference with the Eclipse
Foundation once we pick a time that will work for all.
Thanks,
Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: org.jivesoftware.smack3.psf
Type: text/xml
Size: 249 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/c3941f
62/org.jivesoftware.smack3.xml
------------------------------
Message: 4
Date: Sun, 01 Apr 2007 13:54:45 -0800
From: Scott Lewis <slewis@xxxxxxxxxxxxx>
Subject: Re: [ecf-dev] smack 3.0.0 availability: please respond if
working on voip
To: "Eclipse Communication Framework (ECF) developer mailing list."
<ecf-dev@xxxxxxxxxxx>
Cc: "Roland N. Fru" <roland@xxxxxxxxxxxxxx>
Message-ID: <46102A25.2080405@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: org.jivesoftware.smack3-anonymous.psf
Type: text/xml
Size: 241 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/c50669
e1/org.jivesoftware.smack3-anonymous.xml
------------------------------
Message: 5
Date: Sun, 1 Apr 2007 17:34:56 -0500
From: Chris Aniszczyk <zx@xxxxxxxxxx>
Subject: Re: [ecf-dev] Refactoring/Remodelling/Renaming Call API
To: "Eclipse Communication Framework \(ECF\) developer mailing list."
<ecf-dev@xxxxxxxxxxx>
Message-ID:
<OFD1B1B074.45348A87-ON862572B0.007C03BE-862572B0.007C0C8A@xxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/f3de39
5e/graycol.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url :
https://dev.eclipse.org/mailman/listinfo/ecf-dev/attachments/20070401/f3de39
5e/ecblank.gif
------------------------------
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
End of ecf-dev Digest, Vol 21, Issue 2
**************************************
