Jim Mountford
Senior Member
Hi Mike,
The tag medium.jpg has to do with the size I am posting it. At Pbase they give me a choice, small, medium, large and original. I like to post here in medium in most cases because of download time is pretty small, with a link to a larger version if a person chooses. However, I can eleminate the medium tag all together and post it ending with just the number with a JPG at the end. In that case, I believe it will come in as the original, far too large for here.
What I'm curious about is the bmp image you are talking about. I may be wrong, but it seems to me that I.E. dowloads it as a jpg and through some kind of interpratation by I.E. it changes that to a bitmap for publication in the browser, but if you downloaded it onto your hard drive, it then places it back as a jpg. Like I said, I could be wrong and full of sh*t or worse. But in anycase, when I uploaded this image, I did it as a jpg at about 90K. And consistantly, on my machine and others (that did not have it captured in the cache) it downloads and saves automatically as a JPG at about 90K.
What it boils down too, if everyone had fast connections then this issue would not be an issue. But, many would love better connections, yet technology has not reached them, so they have no choice but to dialup. That is why I try to post small files on here and Pbase.
Peace
Jim
I believe in the KISS principle, 'Keep It Simple Stupid' The more junk you carry, the less effective you'll be because you're always worried about the mechanics, instead of focusing on the subject.
See my gallery at:
http://www.pbase.com/sailingjim/galleries
The tag medium.jpg has to do with the size I am posting it. At Pbase they give me a choice, small, medium, large and original. I like to post here in medium in most cases because of download time is pretty small, with a link to a larger version if a person chooses. However, I can eleminate the medium tag all together and post it ending with just the number with a JPG at the end. In that case, I believe it will come in as the original, far too large for here.
What I'm curious about is the bmp image you are talking about. I may be wrong, but it seems to me that I.E. dowloads it as a jpg and through some kind of interpratation by I.E. it changes that to a bitmap for publication in the browser, but if you downloaded it onto your hard drive, it then places it back as a jpg. Like I said, I could be wrong and full of sh*t or worse. But in anycase, when I uploaded this image, I did it as a jpg at about 90K. And consistantly, on my machine and others (that did not have it captured in the cache) it downloads and saves automatically as a JPG at about 90K.
What it boils down too, if everyone had fast connections then this issue would not be an issue. But, many would love better connections, yet technology has not reached them, so they have no choice but to dialup. That is why I try to post small files on here and Pbase.
Peace
Jim
--This is a very plausible explanation.
I have no knowledge of how pbase works but if you view the source
code to Jim's post you will see that the image links to a file
called "medium.jpg" leading me to believe that they are recreating
the images with their own names and based on display size.
Furthermore there is no reference to a bitmap file anywhere in the
code yet I get a bitmap when I download the image. This means that
there is a switch being performed on the fly, probably by pbase.
This could very well be a script running on a pbase server,
dpreview server or both.
Good call, Mike.
--Jim, I know that mike has read both of my other posts in this
thread. Just to gain a bit more knowledge, you might do the same.
To you both...
Jim only uploads the version of the file Pbase tags as 'original'.
The various other sizings are Pbase constructs, and it makes them
on the fly. That is, it does not stash a 'small' or a 'medium' or
a ..., it makes a newly constructed image when it receives a
request for one. This is one of the things that can make Pbase
provided images such a pain on a site like this. They do not
always end up in your PC cache, so when you are traversing a thread
and come across the same image once again, it does not come out of
your home cache (which would be near enought to instantant), Pbase
once again constructs them.
Right now, Pbase seems to be having some issues. Even though, when
Pbase images are brought up in a seperate window, they show a
'.jpg' suffix, It just might be possible Pbase is providing a
'.bmp' file.
And Jim, my copy of IE 5.5 has no option controlling this in its
set of options. and like I said in my other post to this thread,
one of my photographs served from my web host to this site, does
download as a true jpeg. And that is the only option IE gives me
for its download.
My best,
Ed
--
http://www.blackmallard.com/cal_ls/
California Light and Structure
http://www.pbase.com/mikefam/
I believe in the KISS principle, 'Keep It Simple Stupid' The more junk you carry, the less effective you'll be because you're always worried about the mechanics, instead of focusing on the subject.
See my gallery at:
http://www.pbase.com/sailingjim/galleries