The trick lies in making the customer change their idea about what they want
without realising that you are doing so...

( Unfortunately for some reason that Ive never fully understood they get all
annoyed when you just tell them straight that their requirements are a load
of #### and that it should be done <this> way...
They actually seem to prefer a polite explanation of the drawbacks to their
approach and why the alternative way will benefit them more.
Thats muggles , uh... I mean  users for you. Quite illogical creatures
altogether. Glad to say in my current position I don't have to interface
directly with them much and can concentrate on cutting code. Quite a
refreshing change. )



-----Original Message-----
From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 10, 2002 21:30
To: 'Struts Users Mailing List'
Subject: RE: jsp size limit?


You would build a shitty house because the customer wants it that way?  I
take pride in what I engineer, and there are plenty of customers for which
to work who appreciate that without having to sacrifice professional
integrity.  But then, I'm glad there are people like you to suck up to the
morons of the world.  It gives me something to show clients on how NOT to do
it.

Mark

-----Original Message-----
From: Andrew Hill [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 10:45 PM
To: Struts Users Mailing List
Subject: RE: jsp size limit?


As much as the customer wants.

-----Original Message-----
From: Joseph Barefoot [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 10, 2002 08:45
To: Struts Users Mailing List
Subject: RE: jsp size limit?


True.  'Course, that begs the question:  how much content should you really
have on a single page?

> -----Original Message-----
> From: Arron Bates [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 09, 2002 5:25 PM
> To: Struts Users Mailing List
> Subject: Re: jsp size limit?
>
>
> Not really. It's a whopping class, and it's only really become an issue
> with JSP's, because people can throw in so much content, tags etc.
>
> Arron.
>
> Joseph Barefoot wrote:
>
> >Is this really such a bad thing?  If someone is writing java classes that
> >compile to >64K, I think they may need to revisit their object-oriented
> >principles. ;)
> >
> >>-----Original Message-----
> >>From: Malcolm Dew-Jones [mailto:[EMAIL PROTECTED]]
> >>Sent: Thursday, May 09, 2002 12:19 PM
> >>To: Struts Users Mailing List
> >>Subject: Re: jsp size limit?
> >>
> >>
> >>
> >>
> >>
> >>On Thu, 9 May 2002, Arron Bates wrote:
> >>
> >>>There's a limitation on the size of a compliled Java class. Java has
> >>>this arbitrary limit of 62k for a compiled class. Looks like you're
> >>>
> >>In 1986 Macintosh computers had the same 64K code barrier.
> Compiled units
> >>of code had to be split into chunks that were smaller than 64K,
> and linked
> >>together.
> >>
> >>I guess Java isn't really such a modern language after all.
> >>
> >>
> >>
> >>--
> >>To unsubscribe, e-mail:
> >><mailto:[EMAIL PROTECTED]>
> >>For additional commands, e-mail:
> >><mailto:[EMAIL PROTECTED]>
> >>
> >
> >
> >--
> >To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> >For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> >
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to