Dynamic Content - Temporary Data Storage

  2008-09-22 21:00:03
I have one last item I would like to discuss pertaining to the use of html forms. That is, the question on how to store unvetted, input data. I will show it makes sense to store the news items as formatted, ready to publish summaries as separate text files each containing one story. I further suggest they be deposited in an off site directory with severely limited access rights. The formatting for news items is simple, using either a template or an informed (trained) user. I show how I would have implemented a simple file naming structure to make news items easier to work with in an inherently date / time ordering. For this particular, limited instance, I think my model would have worked. 
  PNG Image  PNG Image  PNG Image
  Related tags  


This particular article has been collected via RSS syndication. We apologize if it's too brief.
If You wish to publish articles on LinuxStreet.net please contact us.


  Similar articles found on LinuxStreet  
ImageTip from an RHCE: Memory storage on PostgreSQL
ImageDynamic Content - Simply Adding from External Source
Image10 free storage utilities
ImageMapping the Future of Open Source Data
ImageStorage solutions for SMEs
ImageCreating an oBAMP Stack: OpenBSD, Apache, MySQL, and PHP
ImageSecure Web Input - Data Analysis
ImageDynamic Data Structure Switching
ImageHowto install a content filtering and virus checking proxy (Part I)
ImagePython Data Persistence using MySQL

Leave a comment on this article


Captcha

  
Check this if the code you see is not readable and resubmit the form.
(Data you entered will be preserved)



  

Comments (0)