I actually go a step further and redefine the img tag altogether (there
are other tags I modify also). In my case, I have an image database in
my system that I often make reference to in static documents and it's
nice to be able to say
img src=dbid
or
img src=img_name
I also take the opportunity to insert width and height arguments, put in
mouseover text, etc.
And, of course, I can use this to automatically refer certain types of
documents, directories, etc, to another server, on my machines or
another. It's also totally transparent to any users, if you want it to
be, because they can keep using the img tag like normal, (or the anchor
tag, or the embed tag, whatever)
Rusty
Jade Rubick wrote:
What's nice about this model is that you can plug in external content
hosting services quite easily.
Jade
On 8/8/07, *Tom Jackson* < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
I know it doesn't require any patches, but you can offload your
image server
pretty easily, very efficiently as follows:
<img src="<%= $Template(gserv) %>/graphics/soa-logo4.gif"
height="33" width="246">
Where Template(gserv) is set for each page request, obviously this
could be as
simple or complex as needed. In this case I offload the graphics
to another
port and serve with publicfile. Don't know if this is faster or
not, but it
doesn't require running through a lot of application code just to
serve up a
public image. Maybe the pure tcl image server would work just as good?
But you can't offload with an https service since the files should
come from
the same ip:port, or at least this used to be required.
Example is for
http://saleonall.com/cat/allcat.html
and
https://saleonall.com/cat/allcat.html
One thing the AOLserver community can offer is examples like this
of how to do
something pretty commonly needed as a website grows in size.
Last week I had example of using threadpools to serve image files
(either old
or new version would work in this case). If there was a way to
configure the
interps in these threads, you could create a series of
micro-servers targeted
to the content being delivered.
tom jackson
On Wednesday 08 August 2007 12:12, John Buckman wrote:
> >> as far as what lighthttpd and mathopd are doing to get better
speeds,
> >> is that they both are not multithreaded, they are just a
single async
> >> loop, serving static files. I remember that this was an
option in
> >> Aolserver v2, but I believe it went away in v3.
> >
> > Gustaf Neumann of WU-Wien patched AOLserver to do asynchronous
> > background delivery, and has been using the feature heavily since
> > 2005:
> >
> > http://openacs.org/xowiki/weblog-portlet?ptag=asynchronous
<http://openacs.org/xowiki/weblog-portlet?ptag=asynchronous>
> > http://openacs.org/forums/message-view?message_id=482221
>
> Very nice. The only thing I'd change would be to have this not
> require Tcl, but rather to have registered file types that are
> automatically sent via the async method (ie mp3/zip)
>
> So, what's involved with having the patch applied to cvs?
>
> -john
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
with the body of "SIGNOFF AOLSERVER" in the
> email message. You can leave the Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave
the Subject: field of your email blank.
--
Jade Rubick
Senior Developer
United eWay Volunteer Solutions
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
tel (503)285-4963
fax (707)671-1333
www.UNITEDeWAY.org <http://www.UNITEDeWAY.org>
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in
the email message. You can leave the Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
