Hi Jim,
the main benefit of the automatic discovery is not really usable in JavaScript client. On
desktop client you can create account settings like:
[server] [port]
[username]
[password]
and it will work because the desktop client can make ANY requests to ANY server (and will
find the destination URL). In JavaScript you can make queries ONLY to YOUR server
(server/port where the client itself is installed), or server which returns proper CORS
headers (I don't know about any server which returns these headers by default - you
always needs manual server tweaking or patching).
In this case the "simple configuration" advantage is gone ... so if we already
needs an experienced admin for proper setup (who knows the proper URL), why to make
another query each time you login? ... it will only prolong the login time ...
JM
On May 28, 2013, at 9:46 PM, Jim Seymour <jseymour(a)LinxNet.com> wrote:
From another thread...
On Mon, 20 May 2013 07:17:56 -0400
Ken Murchison <murch(a)andrew.cmu.edu> wrote:
[snip]
BTW, rather than having the admin specify the path to user principals
in config.js, you should look into doing your discovery by doing a
PROPFIND on /.well-known/caldav for DAV:current-user-principal, and
following any redirects. See
http://tools.ietf.org/html/rfc6764
What are the odds of this happening?
Thanks,
Jim
--
Note: My mail server employs *very* aggressive anti-spam
filtering. If you reply to this email and your email is
rejected, please accept my apologies and let me know via my
web form at <http://jimsun.LinxNet.com/contact/scform.php>.