-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 4, 2007, at 3:30 PM, Jeff Breidenbach wrote:
Maybe a way to think about this is that the canonical url is based on the message-id, but then there's some way to distill even this down to a tinyurl or simple integer that would be stable in the face of full archive regenerations.
I'd suggest the reverse. Keep the canoncical archive URL short and sweet, and then use a URL redirection service to map message-id's to those URLs. It is the archiver's job to make it all work. For
example, the canonical archive URL might stay exactly the way it is in
pipermail. But the archival link embedded in the message would instead go to a redirection service.
I agree. My proposed global message id is exactly the canonical
archive URL, although it's relative to the archiver's base url, as
given in the List-Archive header.
The one other thing I'd ike to revisit is integration with third party archival services. There are two obvious integration points; one is a button in the Mailman list admin user interface that says "archive
with service X" not unlike the setting in Firefox that basically says
"search with service X".
I think we could define an interface that archive services would have
to meet in order to be available to list admins. The site admin
would of course have to enable them site-wide first. Why kinds of
information would be required?
The nice thing is that if my global id idea works, the injection
process can be completely asynchronous.
The other integration point is the archival link discussed above. In which case it would be set to something like.
All we'd need to know is the third party's List-Archive header
value. The last part of the path would always be the global message id.