I'm with you, I prefer in scripting languages to have a single file to hold most of my project so I can backup and work on it anywhere easily.
I used to store page output to a variable in PHP and add to it as the code executed, sending to the user only at the end of file and just trashing that variable if there was an error. Sounds similar to what you're hinting at. On Sep 14, 1:44 pm, OvermindDL1 <[email protected]> wrote: > On Mon, Sep 14, 2009 at 2:40 PM, PatHaugen <[email protected]> wrote: > > > OvermindDL1, > > > The way you describe it, "anything they have sent to the page > > previously is erased and only the error stuff is returned" sounds like > > you're not stopping at the exact point of error, but continuing to > > draw the rest of the page as the code continues and only after that > > erases what was generated and return only the error page? > > No, I do stop at the point of error, but in my design, page output and > code is intertwined (keeping down on file count), so by the time, say, > a database access may fail then stuff may have already been sent to > the sender, I wipe that clean. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
