[Mailman-Developers] Improving the archives

[Barry Warsaw]

-----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.

> http://mail.codeit.com/pipermail/zcommerce/2002-February/000523.html
> http://mail.codeit.com/msgid?002701c4eb3d$07170ca0$3142003e@ADSL
>
> 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?

- - List-Archive base url
- - Message injection procedure
- - Additional subscription procedures

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.
>
> http://third-party-service/msgid?002701c4eb3d$07170ca0$3142003e@ADSL

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.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQCVAwUBRqCqSnEjvBPtnXfVAQJq7gQArkmEb3DqrOaRTdYnQ0SCOrqWtiPxNJOd
555+JiHt/mEqPTuS/cF1GfdckwrQXbUJYWeO56dXzfbXtCVaW54h4k/95RI2/mqK
HR2BKcoVW/dDfYUd2V2Vbqdc7trVIy3oGdzQb24Pu9bIptqbdVSpnmx8jm9GIOi1
UAkJp+Ff5nc=
=lE32
-----END PGP SIGNATURE-----