[
Lists Home |
Date Index |
Thread Index
]
Michael Champion wrote:
> What if I'm looking for John Smith and don't know his person-id? Or
> whether it is Smythe or Smyth... or Jon, or Jan ... or which office
> he works in? A centralized name disambiguation and forwarding
> service would come in very handy.
Agreed. There is always a need for reference by description (and that
need is not a bug). The beauty is that you can have both; they're not
exclusive. That's why I mentioned search earlier.
> Or, consider those acm.org forwarding addresses many of us use ... why
> not expose the actual email address?
You mean like 302 redirects ;)
> I suspect a) we don't want to
> expose the real address to slimeball spammers, b) we want to be able
> to keep the same logical address if one changes "implementation
> details" such as employer, ISP, etc. c) we want a centralized point of
> management (at acm.org) for this and other personal metadata we choose
> to make public. Similar reasons apply to the address example.
Agreed. Central management is good, but uniform management is as good,
if not better. The beauty is that you can have both; they're not
exclusive. That's why I mentioned RSS earlier.
> *if* your users do far more read operations than create/update/delete
> operations, and there is a high probability that a document that is
> retrieved once will be requested again soon.. Very true on the Web.
> Not true for data enty applications. Nightmarishly difficult in the
> distributed read/write case.
Don't understand the last bit - nightmarishly difficult how? For the
firs bit, data entry, being able to ask the system you've entered the
data to what the current state is now is a big win. The only time
systems don't fail is where they're on whiteboards ;)
cheers
Bill
|
