🚀 go-pugleaf

(Hi Alan!)

I'm not at all familiar with the DB architecture of Lotus Notes... however,
a comment you made in your (very helpful) description of that system begs
for elabration:

In article <WEX.90Mar19131959@sitting.pws.bull.com> wex@sitting.pws.bull.com (Buckaroo Banzai) writes:
> - Notes uses a custom, highly-optimized, fully-replicated database to store
>documents.  Documents are seen through hierarchical views.  Views are
>predefined for each DB, though users can define "custom views."  {this is
>their biggest luze, imho.  A replicated DB is a disaster waiting to happen.

Why is a replicated DB a "luze" for such groupware applications? How would
*you* build a DB to share such information? Would your dream system do
queries on a remote databases, and have that information come back in
"realtime"?? What object granularity would you be able to support?

What about situations where notes sites are not connected by fast networks??

Isn't USENET news a slimy form of replicated DB? It seems to work ok...
though it doesn't really offer very much functionality.

-------------------------------------------------------------------------------
	    Niels Mayer -- hplabs!mayer -- mayer@hplabs.hp.com
		  Human-Computer Interaction Department
		       Hewlett-Packard Laboratories
			      Palo Alto, CA.
				   *