Edward Vermillion wrote:
Or just break the "page" up into sections and grab subsequent sections from the DB. (?)
that, or any number of other ideas. but I know from experience that offering seperate records for each section generally leads to a less intuitive (read: easy to use) editing interface (or conversely an editing interface that is alot more work to build).
That way you could easily code in a 'jump to page 3 from page 6' type function,
you could/can do that anyway, if you have 'sectioned' content regardless of whether you create the sections programatically (as Jay suggested), parse the content for section markers or (as I suggested) or stuff 'section' into DB records (as you suggested)
and your still just grabbing data and spitting it out with out worrying about sessions getting mangled or
a. who said anything about sessions? b. exactly when do sessions getting mangled? c. you can't code with a few possible error situation in mind? d. what happens when your DB goes down?
parsing for html comments that could get blasted by an errant edit.
the marker is either there or not - and if it'd borked (e.g. '<!-- PAGE MAR') then it would break the page, sure - but so could ANY broken markup so the argument is somewhat moot. besides a routine to strip markers (broken or otherwise) is as simple to write as marker splitting function is. jmho. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
