[Design] freshness, globally unique IDs (size, copying, IDs)

[bkd]

--- "Rys (David) McCusker" <david@treedragon.com>
wrote:

> > I've spoken with John Anderson, our systems
> architect, and with Rys 
> > McCusker about supporting access to external data
> in Chandler.  The 
> > source of external data could be pretty arbitrary
> -- a blog, a Notes 
> > database, SQL server, ad infinitum.
> 
> We discussed the idea of external store plug-ins for
> a repository.
> Where the plug-ins would connect is still an open
> question.  In the
> repository under the protocol?  In a layer on top in
> Chandler clients?
> 
> Alternatively, since our repository will have a
> protocol (RAP), it's
> possible for external stores to simply use the
> protocol to write what
> must be stored locally in a repository.
> 
> Another approach to presenting external stores to
> Chandler is through
> the repository access protocol (RAP) itself.  An SQL
> Server could present
> a face using RAP, and it would be the same as any
> other repository.

It's all about the repository, yo. 
(don't look at me like that...you're the ones who
decided to call the protocol 'RAP')

See my wiki pages about the ChandlerDaemon and the
PalmDesktop. 

In short, access to the repository should run totally
through RAP, be it OSAF's user client, written in
Python and wxWindows talking to the repository daemon
at 127.0.0.1:5000, and corporate server at
10.3.1.3:5000, or a third party's collection of Perl
or PHP CGI scripts kicking out HTML formatted data to
a web browser.

If the process concerns accessing or managing the
repository, be it a PDA sync, instant message,
downloading and sorting email, then it should be
*ahem* RAPping with the Daemon.

Additionally the Daemon should take care of other
autonomous activities, such as scheduled events and
scripts, and new mail notifications. 

> I have long been thinking in terms of mounting
> multiple repositories
> in a Chandler client, as opposed to multiplexing
> many stores in a way
> that makes them look like one repository.

Outlook Express makes it trivial to do this, though
the behavior has to be explicitly configured by the
user. I think It would be better as the default
behavior.

If you have more than one email account set up in
Outlook Express, you're offered and additional filter
criteria: 'comes from account X.' You can then create
a folder, X, and filter everything from account X to
folder X, unless the email is following a higher
priority filter, like all email with 'ebay' in the
subject routed to the ebay folder.

As long as every Chandler object has its source
permanently attached to it as an attribute, it should
be fairly trivial to create a View driven by a query
by source, and build upon it from there.

bkd


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/