RE: images in posts

> Pyblosxom does not support images, as the http protocol goes, 
> if you let pyblosxom deal with images, it will mean that
> pyblosxom will be loaded everytime for an image. That is a
> waste of CPU processes. Store your image files in your
> HTDOCS/images directory, for example, and use
> href="/images/foo.jpg" in your links. This is something the
> webserver will handle better, not any of the *osxoms. I
> believe, this is the easiest most common sensical way.

Just as a side note, this doesn't really work for me.  My
weblog is at http://weblog.latte.ca/ and so /images/foo.jpg
still gets shoved through pyblosxom.cgi, which fails to
handle it gracefully.  So I have links to images in
http://bwinton.latte.ca/camera/weblog/ in my weblog, which
isn't as clean as I might like it to be.

Since this is apparently an itch for me as well, I might
have a go at adding the functionality Sean wants into the
next version of PyBlosxom.  (It would just be a new type
of EntryParser, unless I miss my guess.  It would have to
override pretty much the whole chain of events, so that it
just returned the image, but it might work.

Later,
Blake.



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/