At 12:08 PM -0800 9/16/00, Chris Lott wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>My new site is related to this thread, so I would like to hear
>suggestions about the following issues. The site is largely dedicated
>to serving out a selection of poems, essays, stories, etc. I am
>trying to bridge the gap between relatively easy contributions and
>adequate performance when serving the file (aren't we all?).
>
>1) Should I store the text with HTML formatting? Most of the items
>will have formatting needs (bold, italic, explicit line breaks, and
>of course paragraph breaks) and short of some kind of custom
>shorthand, HTML seems like the best way.
Unless you want to limit or control formatting and replace it with
some meta-language, go ahead and save the text/html as entered.
>2) How should I deal with the input and splitting of longer stories:
>should the user submit the html/text file and then I will have CF
>split the file into different database entries using some algorithm
>for a word count and then split at the nearest sentence or paragraph
>break or ??
How long is longer?. If you are using SQL Server 7.0, a single text
field can contain 2 gig (a varchar can contain 8K). If you use a
text field, then I wouldn't bother splitting the content.
You might want to have a separate field in the table o contain a
short abstract or the first paragraph/stanza.
This way you can display a page with a preview of several
essays/poems with little overhead. The user clicks on a "more..."
button to display/download the entire content of desired articles.
I have used this approach on several publication sites which display
news and magazine articles. Works great!
>3) Could someone explain how I might create tables to handle the
>split text? Should I just have a single table with
>title, partnum, text and then when displaying check if there is more
>than one partnum, or should I have a couple of tables?
I don't think you need to bother to split the content.
>I'm starting to wonder if I should do this with a db-driven site at
>all :) But I've already been tied to doing a CF site with Fusebox,
>though the methodology is largely irrelevant.
I strongly recommend the database-driven dynamic content approach.
It is lot easier to maintain/search/manipulate than thousands of
separate html files.
HTH
Dick
>c
>
>
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP 6.5.8 for message encryption and authentication: USE PGP!
>Comment: PGP KeyID: 0x51046CFD
>
>iQA/AwUBOcPTLdaLYehRBGz9EQLN7ACfdD+BAqox51FmSnOgH4viyOCErlEAn3xH
>HC6gEKOqkWC7Sd0sIzORljjn
>=kDLa
>-----END PGP SIGNATURE-----
>
>
>------------------------------------------------------------------------------
>Archives: http://www.mail-archive.com/[email protected]/
>To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_tal
>k or send a message to [EMAIL PROTECTED] with
>'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
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.
