Hey!
>>>>>>
Eg: database binding:
Servlet uses Connection pool to create ResultSet and then passes each
row back to the client as an HTML page, with JSP, some intermediate
business object code (sitting above ResultSet to provide caching) and
a decent database server this is lovely and easy.
>>>>>>>
I agree here. I do the same. My very first servlet for production got
oohs and ahs because it was so fast.
>>>>>>>
>At the end of the day - I'm not attacking you -
I know that. Nor I.
>but I think that
>applets get used because people don't understand the web architecture
>propely and are happy to code in that old way that we all got used to
I have to admit that my environment is the intranet and not the Internet
where
I have more opportunity to use JApplets with users on high speed networks
as opposed to 56k modem world and 486s, god forgive.
>with X and Windows and so on, but it actually (IMHO) is less of a fit,
>has more *resistance* than using the servlet/webserver architecture.
>>>>>>>
I just couldn't resist your categorical statement and the impression it
could
possibly give to new comers.
Your responses to questions on this list are very much appreciated by me.
Keep up the good work.
Danny Rubis
Nic Ferrier wrote:
> >>> Danny Rubis <[EMAIL PROTECTED]> 10/23/99 4:37:19 PM >>>
>
> >Nic, I disagree again.
>
> Fair enough. It was probably a bit OTT - I had just got up.
>
> >With a good IDE like IBM's VisualAge for Java
> >I can conservatively say that I could have accomplished
> >the same in about two months. I would end up with
> >a hunk of code that was OO as opposed to the
> >JS route, with full power of the Java language and much
> >easier to maintain.
>
> I'm not saying JavaScript is good. Oh no! I try and steer clear of
> that as well if I can.
>
> Maybe it's just about the different things one has worked on. Mine is
> a very web-centric world, I like to work within the web architecture.
> I don't include display applets in that archiecture (but it's not a
> religious thing - I do use them).
>
> But the original question was about database binding to a display of
> the table. In my view this is much better done on the server side, for
> all sorts of reasons I admit but the speed of applets is the primary
> one.
>
> It comes down to the old developer problem, typified by M$ houses
> where developers create apps that run on their high powered
> workstations that run really rubbish when you get them on the 486 and
> Pentium 60s that people still actually use (I know - it's mad).
>
> Applets are part of the same culture to me, I like to turn eveything
> around on the server if I can and use JS for *limited* times when I
> need to have some client side decision.
>
> Eg: database binding:
> Servlet uses Connection pool to create ResultSet and then passes each
> row back to the client as an HTML page, with JSP, some intermediate
> business object code (sitting above ResultSet to provide caching) and
> a decent database server this is lovely and easy.
>
> Don't have to go near JS unless you want something flashy like a drop
> down list or something. Even drop down lists can be done using trips
> to the web server. It's not difficult you just have to think a little
> bit harder about state.
>
> At the end of the day - I'm not attacking you - but I think that
> applets get used because people don't understand the web architecture
> propely and are happy to code in that old way that we all got used to
> with X and Windows and so on, but it actually (IMHO) is less of a fit,
> has more *resistance* than using the servlet/webserver architecture.
>
> >Does anyone have an interactive site using the JS
> >route on the web where I can go for a look?
>
> Depends what you mean. Every webmail service that's ever been writen?
> They're pretty interactive (as interactive as a database browser
> anyway).
>
> I'm work on Talk21 which is BTs free email system (www.talk21.com).
> It has a lot of problems because of history but we're making some real
> progress because of the way we do things. I'm hoping this will become
> a site to illustrate the power of my philosophy. Take a look if you
> like, though it's a pretty standard fee email system right now.
>
> Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
