Heikki Toivonen wrote:
While
this is certainly nice, I think our real goal is getting to the
stage where the repository runs as a separate process on the local
system and possibly also remotely. I don't know if it would be possible
to store that onto a USB or other device.
heh, I didn't even realize the out-of-process repository was a goal!
That does obviously change things.
I guess I'd just hate to see chandler-the-app in the business of
managing profiles. If the repository eventually does go out-of-process
I would hope that it would store its "profiles" somewhere else other
than a user's home directory (on any platform) so I'd hate to burden
the in-process repository logic (and thus developers and QA) with extra
levels of indirection
(that said, I don't mean that we should try to get USB keys working
anytime soon, or even at all.. just that its probably the only
non-developer reason I can think of for an in-process repository to
exist anywhere besides ~/.chandler or equivalent)
Alec
However, it should be possible
to store cryptographic material used by Chandler on such a device - for
example your personal certificate and trusted CA list so that you can
connect to a remote server even in the case where you don't have
locally
cached copy of the repository.
I know I'm late to the game on this one but
IMHO, profile management
should be limited to a command line parameter as described on the Wiki,
and we should not try to do "profile management." The fallout of this
is
that we can/should get rid of the extra two levels of redirection
"Profile/<profilename>" and just use the random seed.
i.e. ~/.chandler/lk8sffkis.rep/ or C:\D&S\alecf\App.
Data\OSAF\Chandler\lk8sffkis.rep
I think it would be easier to have a profile name the user can specify
rather than just generate something at random, even if we only had
command line option to select the profile.
As long as we don't have the repository running in a different process,
I agree it should be possible to do this without UI. To delete a
profile
just manually delete the dir, to create a profile just specify a
non-existing name, to select existing use an existing name.
But if/when we have the repository in it's own process I am pretty sure
we'll need some way of adding and removing accounts, disabling and
enabling accounts and deleting all the data in an account. Since all of
this should be just editing items in the repository, whatever UI we
have
for that would minimally suffice (but I'd really like a separate UI
because you don't want to accidentally wipe accounts or data).
I agree with John that if the repository is
where we (want to) store
everything, then we should call it the "repository directory", and try
See my previous response while I think it is a bad idea to call this
"repository directory". If we do manage to put everything into the
actual repository I could change my opinion. But we'd need to agree not
to write anything else there, like chandler.log etc.
--
Heikki Toivonen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
