Re: [Mailman-Developers] Searchable archives for MM
Args, I knew I forgot sth, I should have selected MIME digest :)
On Thu, Aug 06, 2009 at 22:19:30 -0700, Jordan Hayes wrote:
Here's my solution:
http://infothecary.org/jordan/mailman.html
Nice solution Jordan, but I think about a pythonic way to fully integrate searchable archives into MM. I was using the debian archive search only as an example for what can be achieved on big archives.
Thanks Siggy
bsb-at-psycho-dot-informationsanarchistik-dot-de
or: bsb-at-psycho-dot-i21k-dot-deO< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Siggy writes:
Here's my solution:
http://infothecary.org/jordan/mailman.htmlNice solution Jordan, but I think about a pythonic way to fully integrate searchable archives into MM.
Um, you need Phython in this equation exactly why?
The archives are web pages. Who cares what language was used to implement the search?
You don't demand a Python web server to deliver your archives, do you?
I was using the debian archive search only as an example for what can be achieved on big archives.
For me, I think the people who Think Hard about searching text can work in whatever language they want; SWISH-E has done a good job of providing a platform for search, and it's easily integrated with Mailman. FWIW, I have lots of "big archives" ...
/jordan
On Aug 9, 2009, at 9:31 PM, Jordan Hayes wrote:
Um, you need Phython in this equation exactly why?
The archives are web pages. Who cares what language was used to
implement the search?You don't demand a Python web server to deliver your archives, do you?
Heh, well Mailman 3 will include a couple of Python web servers.
There will definitely be a web server for the REST interface and the
web ui will likely be vended from a Python web server. They're super
easy to write!
Note that we've adopted WSGI for all web protocols so the ultimate
port 80 listener can be almost anything. This will make it easy to
integrate with frameworks such as Zope, Django, Turbogears, etc. or
even Apache through mod_wsgi.
I'm going to need really strong arguments to bundle anything not
written in Python.
I was using the debian archive search only as an example for what can be achieved on big archives.
For me, I think the people who Think Hard about searching text can
work in whatever language they want; SWISH-E has done a good job of
providing a platform for search, and it's easily integrated with
Mailman. FWIW, I have lots of "big archives" ...
The way to think about this then is modularization and pluggability.
The archiver itself is already pluggable (with more well defined
interfaces in Mailman 3). The question is whether for Pipermail, the
search itself should be pluggable. Think about how that would work.
-Barry
Barry Warsaw writes:
Mailman 3 will include a couple of Python web servers.
Sorry, my port 80 is already taken up by something else :-)
There will definitely be a web server for the REST interface and the web ui will likely be vended from a Python web server. They're super easy to write!
I look forward to someone reimplementing in Python a search package as good as SWISH-E :-)
/jordan
On Aug 10, 2009, at 1:09 PM, Jordan Hayes wrote:
Barry Warsaw writes:
Mailman 3 will include a couple of Python web servers.
Sorry, my port 80 is already taken up by something else :-)
Web servers can bind to other ports. They can even be proxied :).
There will definitely be a web server for the REST interface and the web ui will likely be vended from a Python web server. They're super easy to write!
I look forward to someone reimplementing in Python a search package
as good as SWISH-E :-)
If there are Python bindings to SWISH-E, then that might be good
enough for inclusion in Mailman.
-Barry
participants (4)
-
Barry Warsaw -
Jeff Breidenbach -
Jordan Hayes -
Siggy Brentrup