From: "Gary Poster" <[EMAIL PROTECTED]>
> I agree that
> we ought to trash frames
> we ought to use strict xhtml 1.0
> we ought to rely on CSS for all graphic elements
> (correlative) we ought to not use *any* shims or non-logical tables
> the site ought to work completely without JS or
>
> * the immediate correspondence between the request and the
> response containing essential information to analyse the problem
It's application problem and the application have to handle it.
Log all the request/responses on the server or the client side.
>
> * newbies
They have no
From: "Rossen Raykov" <[EMAIL PROTECTED]>
> Shall the dump help the regular surfer? I doubt so.
>
> Shall it benefit the developer or the tester? Most probably not since they
> are not performing their activities on the production site.
Oh, they most definitely help the developer or tester, becau
> > Shall the dump help the regular surfer? I doubt so.
> >
> > Shall it benefit the developer or the tester? Most probably not since
they
> > are not performing their activities on the production site.
>
> Oh, they most definitely help the developer or tester, because errors do
> appear on produc
On Sat, 6 Apr 2002, Rossen Raykov wrote:
> > BUT: The developer has access to the system, and the dump doesn't have to
> be
> > included in the HTML output. Maybe error dumps could be sent to a disk-log
> > of some sort?
> >
>
> Exactly that's my point.
> Log it with as many details as you can!
>
