Billy Crook wrote:
Can you think of a reason why it's important to store that same data
over and over as opposed to just reading some php or apache variable
for hostname or path, or something from config.php?
Since this is an application that supports distributed microblogging, we
have both local and remote URIs in the uri field for notices and profiles.
It would be inefficient to recalculate those URIs based on whether the
notice is remotely generated or locally generated. Every process that
used those database records would need external information (from the
config file) to determine what the URI "really" is.
We use these URIs tens of thousands of times per day; the base URL for a
site changes once or twice or at most 3 times during the lifetime of the
installation. Optimizing for the second use case would be a bad idea.
I agree that changing the server name or path is annoying; I think the
best thing to do would be to have a script that admins can run when they
change those values.
It's clear that should happen where URLs are used as locators (since the
old values may no longer be available), specifically for profiles and
avatars; it's less clear that that should happen when URLs are used as
identifiers.
-Evan
--
Evan Prodromou
CEO, Control Yourself, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
