Err this database already exists...I call it a file system. What would you
dynamically change in an image? Changing the size of an image is already
possible via the <img> tag. Changing resolution on the fly would require
processing power that is way beyond capabilities today, not to mention the
browsers dont support over 72x72...
jon
----- Original Message -----
From: "Dick Applebaum" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 15, 2000 4:40 PM
Subject: Re: Upload and retrieval of stories?
>
>
> Xing
>
>
> Good points!
>
> But, then, why doesn't it, also, make sense to use static html pages
(processed and cached by the web server) and avoid CF & SQL altogether.
>
> A little bit of devil's advocate role playing here. I understand the
advantages/costs/tradeoffs of DDC (Database-generqated Dynamic Content) for
presentation of html pages.
>
> I just think that the same may apply to non-text Content.
>
> The difference I see is that:
>
> text content is likely to change (correct spelling, format, format
option
> for printing, etc)
>
> most non-text content probably won't change (other than be replaced by
> different static content)
>
> This may change in the future as we may want to programatically
manipulate
> non=text content before presentation.
>
> An example might be to reduce the size/resolution (or other
manipulation) of
> an image or sound file before presentation... kind of a dynamic
thumbnail.
> There are programs such as ImageMagik which can do this for images,
probably
> something exists for
>
> If there is a need to maintain a large repository of digital (non-text)
content then a database appears to offer some significant advantages for:
accessing, cataloging, security, referential integrity, backup...
>
> Maybe the advantages of database will change the way non-text content is
stored and served.
>
> How about a "specialty server" optimized for this purpose. This server
would efficiently access and cache large binary files. A request for
content would go directly to the "specialty Server", bypassing both
Application Server and Web Servers.
>
> The "Specialty Server" would receive the request, retrieve the requested
content, attach the appropriate headers/mime-type and serve the content,
directly.
>
> As the web evolves, we may need to change the way we think about non-text
content...
>
> ... what, with applets, embeds, images,etc - what percentage of the
typical page (at the browser client) is actually text?
>
> Apple's new OSX uses Quartz for presentation services... this mean that
everything you see on the screen is in PDF format. (See below).
>
> Does this mean that we could serve PDF pages directly to a Mac Client and
eliminate all plug-ins browser overhead, extra OS Presentation overhead...
probably!
>
> Couldn't the same approach apply to images, audio, video... probably!
>
>
> Just some questions/thoughts.
>
> Sorry for rambling.
>
> * Quartz. Based on the Internet-standard PDF (Portable Document Format),
Quartz is a power-ful
> new 2D graphics system that delivers on-the-fly rendering, anti-aliasing,
and compositing of
> PostScript-strength graphics with pristine quality. Thanks to Quartz,
graphic elements that were
> sharp before are now dramatically sharper-even when their size is greatly
increased. Every-thing
> graphics pros create in 2D will have stunning impact
> .
> Quartz features built-in support for PDF, enabling users to embed and
manipulate PDF data
> with any optimized Mac OS X application. Users can also "print to PDF,"
giving them the ability
> to output any document as a PDF file. So you can easily create
Quartz-enhanced, graphics-rich
> documents that can be shared with anyone. Since this capability is
available to all Mac OS X
> applications, Macintosh developers now have a whole new palette of
creative tools at their
> disposal.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
