tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Punte" <ste...@hamsoft.com>
Subject Re: Interactive Pages: Was passing parameters to a bean
Date Wed, 05 Apr 2000 22:18:51 GMT
Subject: Re: Interactive Pages: Was passing parameters to a bean


> Why not use 2 Frames - select the state etc in the top frame - causes
> query to servlet directed to the bottom frame. Minimum traffic.


    My goal is to emulate as close as possible a monolithic
    interactive "application."  An application were fields
    have multiple interactions with other fields.  The two
    frames is a crude cut at this, but I'm attempting to
    achieve a more conventional dynamic look and feel.

    Steve



> > Steven Punte wrote:
> >
> > I've been following the "Passing parameters to a bean with JSP"
> > thread with fascination.  I think I basically have the same issue,
> > but
> > can more easily be put fourth as the following example:
> >
> > Browser                                            Server
> >
> >
> >         <--------------------------------------  Send Page
> >
> > User Enters zip code -------------------->>>
> >
> >         <--------------------------------------  Send City and State
> >
> >
> > The desire behavior is to have city and state automatically
> > filled in once the zip code has been specified.
> >
> >
> > As I see it, there are several approaches:
> >
> > 1)    Re-send a complete new page once zip code
> >         has been entered.  Drawback: significant
> >         information is being send a second time.
> >
> > 2)    Send mapping of zip -> { City, State} in original
> >         web page as JavaScript Arrays.  Drawback:
> >         not scalable to situation were database is very
> >         very large.
> >
> > 3)     Use Applet instead of form.  Drawback:  loose
> >          thin-client simplicity and robustness.  Also applets
> >          and HTML have little interactivity.
> >
> > 4)    "Pushlets" as defined in
> >
> > http://www.javaworld.com/javaworld/jw-03-2000/jw-03-pushlet.html.
> >         I could use another opinion here, but this certainly doesn't
> >         feel like an elegant robust solution.
> >
> >
> > In summary, I too am looking for a better solution.  It would
> > really be nice if:
> >
> > A)    Can JavaScript itself open socket communication
> >         back to the server?
> >
> > B)     Could JavaScript communicate to a non-visual applet
> >          that communicates back to the server?  Boy, this
> >          sounds complicated again.
> >
> > C)     Could some custom plug-in be a big help here?
> >
> > STeve Punte
> > stevep@technologent.com
>
> --
> WBB - wbrogden@bga.com  Chief Scientist, LANWrights, Inc.
> Java Programmer Certification information and mock exam
> at  http://www.lanw.com/java/javacert/
>
> --------------------------------------------------------------------------
> To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commmands, email: tomcat-user-help@jakarta.apache.org


Mime
View raw message