emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: emacs-orgmode@gnu.org
Subject: Re: MobileOrg on DropBox for Teams
Date: Sun, 28 Nov 2010 09:54:37 -0600	[thread overview]
Message-ID: <m239qla1fm.fsf@verilab.com> (raw)
In-Reply-To: 1290955261.27101.1407521573@webmail.messagingengine.com

"Richard Moreland" <rlm@ncogni.to> writes:
> ... I'm not sure how your account sharing is setup:  if you are all using
> the same credentials, you will probably run into trouble. ...
> ...
> The other option is to let each user have their own Dropbox account and
> simply share folders from a master account to each person.

DropBox For Teams is a third option[1]. Teams gives you a block of
shared space and a set of accounts (each with their own authentication
credentials) that share that space. The entry level is 350G of space and
five accounts. 

From an authentication point of view, it acts just like each user having
their own DB account. However, the difference is that with Teams,
everyone has access (assuming the sharing allows it) to the full 350G of
space[2]. 

Actually ... I've just realized that there's no problem. Every user
*can* have their own MobileOrg at the DB root, provided they don't share
it with anyone else. In fact, even if they did share it, it would merely
appear in someone else's view with a number appended to the name (just
as happens right now if there's already a MobileOrg folder in DB when
MobileOrg first starts). But then I don't know what the iPhone client
would do if it spotted multiple genuine MobileOrg "(n)" folders at the
DB root.

But I think the general solution -- in a DB for Teams environment --
would be to recognize that the entire DB space is being shared among
separately authenticating users, a la a set of unix home
directories. I'm willing to bet that as Teams develops (it must still be
in beta, hence it not being advertized) its multi-user-ness will become
more obvious and demanding of app support.

OK - conclusion. No change needed on anything right now. It's all
good[3]. 

Tommy

[1] We've been using it for over a year now but AFAICT it's still not
being advertized.

[2] Compare an entry-level DB for teams -- five users, 350G of space --
with five completely individual accounts, each with 70G. If no one is
sharing anything (and DB is being used by each user merely only to sync
personal data among multiple machines) then they're pretty much the same
thing, assuming an even share of the 350G in the Teams case. But when
sharing, Teams is better. With Teams, the maximum shared space is 350G,
whereas with the individual accounts the maximum is still only 70G.

[3] But if the Teams edition is to be embraced, then making the location
of the MobileOrg files controllable *from within the setups of both
emacs and the mobile device* (as opposed to after setting up, via a move
of the folder) is probably advisable.

      reply	other threads:[~2010-11-28 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 19:18 MobileOrg on DropBox for Teams Tommy Kelly
2010-11-27 19:31 ` Richard Moreland
2010-11-28  5:01   ` Tommy Kelly
2010-11-28 14:41     ` Richard Moreland
2010-11-28 15:54       ` Tommy Kelly [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m239qla1fm.fsf@verilab.com \
    --to=tommy.kelly@verilab.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).