<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Why don't you simply get the filesize of the image the client is about<BR>
to upload (via client script) and hit him with the message: "this file is <BR>
to large\n the file must be smaller than...," etc.<BR><BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <BR> Troy III <BR> progressive art enterprise<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR><BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Thu, 12 Jul 2007 08:00:18 -0400<BR>> To: javascript@LaTech.edu<BR>> From: tedd@sperling.com<BR>> Subject: Re: [Javascript] Resizing images client-side<BR>> <BR>> At 5:42 PM -0400 7/11/07, Terry Riegel wrote:<BR>> >Ok I see, to save bandwidth then. Because if you resize at the <BR>> >server you can dump the original file. The only thing lost is the <BR>> >user spent a little more time getting it to you.<BR>> ><BR>> >Terry<BR>> ><BR>> <BR>> Terry:<BR>> <BR>> Yes that, but it's a bit more. One, not only does the user tie up <BR>> their bandwidth, which sometimes the user blames on the site, but the <BR>> server receives a hit in two ways. One, if has to spend the time and <BR>> memory to receive the large file, and two, it then has a larger file <BR>> to reduce.<BR>> <BR>> If the user would trim their files to begin with, then there wouldn't <BR>> be a problem. However, educating users is another subject.<BR>> <BR>> Cheers,<BR>> <BR>> tedd<BR>> <BR>> -- <BR>> -------<BR>> http://sperling.com http://ancientstones.com http://earthstones.com<BR>> _______________________________________________<BR>> Javascript mailing list<BR>> Javascript@LaTech.edu<BR>> https://lists.LaTech.edu/mailman/listinfo/javascript<BR><BR><br /><hr />Don't get caught with egg on your face. <a href='http://club.live.com/chicktionary.aspx?icid=chick_wlmailtextlink' target='_new'>Play Chicktionary! </a></body>
</html>