Replacing the *open standard* LDAP with dependency on a
*single vendor*
*proprietary* protocol is a bad solution. How many orgs are
running a
Google contact DB on their LAN/intranet? Vs how many running
LDAP? How
much existing Google API SW is there for the many different
solutions,
vs the huge LDAP community's?
Of course the best S-C architecture would make the contacts
network
protocol a plugin with a consistent internal API. But by far
the most
productive default plugin would be LDAP.
On Tue, 2007-08-28 at 16:18 +0200, D. Lazreg wrote:
> Hi,
>
> Google database could be another solution.
> Check out API and you see !
>
> Dennis
>
>
>
>
> Chris <sipcom cyberspace7.net> a écrit :
> Hi,
>
> I totally agree with Matthew concerning the
contact-list
> transfer. FTP wouldn't
> be a good choice at all and wasn't really meant
for that,
> whereas LDAP seems the
> most obvious choice and probably the easiest to
implement.
> What's more, we could
> add support for central directory services
afterwards. This
> way telephone
> directories could be queried to find &
contact people which
> aren't in the
> contact list.
>
> Sympho: About the privacy concerns, using
LDAP would enable
> us to
> take advantage quite easily of TLS (ex-SSL,
using
> StartTlsRequest) to secure the
> transfer on the network. But if I understand
correctly, what
> you're talking
> about is avoiding to have private data leak out
of a
> third-party server. I guess
> that we could find a way to send the
contact-list already
> crypted to the server,
> but I don't know if it's really worth the pain
(and it
> probably wouldn't be 100%
> secure). Anyway, as you suggested, somebody
could always host
> his own LDAP
> server if his contact list is so sensitive ;).
>
> Cheers,
> Chris.
>
> Selon Sympho :
>
> > Hi Thomas,
> >
> > Thomas Hofer a écrit :
> > > Hi!
> > >
> > > One idea we have is a centrally
stored contact list for
> sip. I miss this
> > > feature in sipcommunicator now, but I
would develop it as
> a plugin. I think
> > > about exporting the contact list into
xml (as it is stored
> locally) and
> > > upload it to an ftp-server, and
download it on startup.
> > >
> > > Has anyone thought about such a
feature and probably
> thought about some
> > > reqirements?
> > >
> > >
> > Yep, I have tought about it sometimes ago,
and I think it
> will be great
> > to have such a feature.
> > The main "problem" I see is
privacy concerns.
> >
> > When someone has an account on some
server, it is obvious
> that this
> > server stores its personal data.
> > But what about storing them elsewhere ? If
the user can have
> a "trusty
> > server" it is OK.
> >
> > Regards.
> > > Yours, thomas
> > >
> > >
>
------------------------------------------------------------
---------
> > > To unsubscribe, e-mail:
> dev-unsubscribesip-communicator.dev.java.net
> > > For additional commands, e-mail:
> dev-helpsip-communicator.dev.java.net
> > >
> > >
> >
> >
>
------------------------------------------------------------
---------
> > To unsubscribe, e-mail:
> dev-unsubscribesip-communicator.dev.java.net
> > For additional commands, e-mail:
> dev-helpsip-communicator.dev.java.net
> >
> >
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail:
> dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail:
> dev-helpsip-communicator.dev.java.net
>
>
>
>
>
>
____________________________________________________________
__________
> Ne gardez plus qu'une seule adresse mail ! Copiez vos
mails vers
> Yahoo! Mail
--
(C) Matthew Rubenstein
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
|