[Design] introduction and a few ideas.

[petite_abeille]

On Monday, Oct 21, 2002, at 10:17 Europe/Zurich, christopher neitzert 
wrote:

> Perhaps this is another thread, yet it seems that a localized 
> Relational
> Database coupled with a LDAP-like public index of the contents of the
> Database is the 'server like' functionality this application would need
> on the client side to empower the user with complete usability between
> clients without an infrastructure to support it.

Something like LDAP could tackle another issue: addressability. This 
just means that any object/entity in the system could/should be 
directly addressable from the outside: have an url (or multiple urls) 
pointing to it. That way information residing in the system are 
transparently accessible to anybody speaking the right protocol. For 
example, emails can manifest themselves through a traditional email 
client, but also through an IMAP url pointing to them directly. Or 
through a NNTP group encapsulating an entire thread. Or through ftp to 
point directly at an attachment. Or through a calendar event. And so on.

Also, keep in mind that the data itself does _not_ belong to the 
application: it belong to the user. Making any data addressable through 
standard protocols make moving data in and out of the system a breeze. 
Which is a "good thing" as nobody want to be stuck in any particular 
system with its very own data buried under multiple layer of 
proprietary format.

PA.