OT: AJAX, XML and fpcgi (formerly fpCGI failure, part 2)

Tyler tyler.style at gmail.com
Wed Mar 19 14:39:29 PDT 2008


> Date: Wed, 19 Mar 2008 13:04:37 -0400
> From: Fairlight <fairlite at fairlite.com>
> Subject: Re: fpCGI failure, part 2
> To: filepro-list at lists.celestial.com
> Message-ID: <20080319130437.A13300 at iglou.com>
> Content-Type: text/plain; charset=us-ascii
>
> Four score and seven years--eh, screw that!
> At about Wed, Mar 19, 2008 at 09:16:02AM -0700,
> Tyler blabbed on about:
> > Just in case anyone's still interested in my fpcgi saga, here's an
> update.
> >
> > Adding an entry to the submitted forms for the nohtmlreturn field didn't
> > resolve the issue.  There were minor bomb outs (meaning the filepro
> > processing didn't run and no output was produced) throughout testing,
> but
> > after about 5 days it stopped outputting anything for any report.
> >
> > Working with fptech on the issue, so may have more to follow up with
> after
> > speaking with them.
>
> By the time you've reached this point, you could have migrated to OneGate
> and been done with all these problems, more than likely.  And had better
> security and more features.  And a lower Tylenol bill.
>
> You mentioned doing AJAX work with fpcgi.  How are you getting around the
> inability of fpcgi to change MIME types on errors?  Browsers are -really-
> picky about the type for the response to the XMLHTTPRequest object.  Or is
> it just really ugly when it errors?  :)
>
> mark->


I'm not actually sending back XML documents at all.  They are inefficient
and impractical for Javascript for most purposes (and especially mine, where
mostly chuck small datagrams back and forth).  I use JSON instead, and have
a parsing/validation class that uses eval() to instantiate the data if it
passes all the checks on the fly as an object literal.  Some people complain
about JSON not being human readable, but I myself rarely have that problem.
Probably from staring at them too long in general :)

Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20080319/0030591d/attachment.html 


More information about the Filepro-list mailing list