On Thu, Mar 03, 2005 at 11:20:16AM -0500, Martin G. Diehl wrote:
For what it's worth, I suggest the use of static web pages
that will work on *all* browsers.
You bring up something I had completely missed.
(Long thoughts on something very, very simple. If this is an
issue at all, it's more of a long-term, year-away thing to think
about than something important to get set straight within a week
or so.)
I had assummed that we merely needed a "really-cool-spf-site.com"
name, and that then we could push that site instead of spf.pobox.com
both for the official spf site (with links to all sorts of documents,
this list, maybe forums if someone wants to both set up and maintain
that, etc) *and* for these error messages and related new-user intro.
I wasn't thinking of the potential scaling problems of having both
sets of functionality on the same site.
While most folks here will be familiar with having static pages on
an otherwise dynamic site, (or pages in some way compiled to be static),
such that the static pages will be cached and the dynamic ones not,
and most folks are familiar with handling the scaling issues involved,
I for one am slightly concerned about the logistics of having a site
containing a relatively small section that will be very active for at
least a decade, and that should be admin-able by a number of people,
that should have an uptime comparable to the root dns servers, etc,
that's is also run alongside a more ephemeral site/set of pages.
So I would suggest that perhaps the static pages referred to in error
codes point to a separate host and url that is *just* for that sort of
thing, so these can be kept up for a long time, and more easily restored
in case of problems with a more complex spf.pobox.com equivalent as that
other side grows/shrinks/changes.
(ie, maybe there could be a messages.spf-cool-site-name.com that could be
a single-page site, or a separate one-page spf-messages.com site that
points to spf-cool-site-name.com for those who want more info.)
Categories ...
All good points.
-Mark Shewmaker
mark(_at_)primefactor(_dot_)com