tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Layman <randy.lay...@aswethink.com>
Subject RE: best way to handle Servlets+JSPs+multiple Frames?
Date Wed, 21 Feb 2001 17:26:19 GMT

	But I think that his orginal point was this does not seem like an
efficient solution - you end up loading the frameset for every page, as well
as all the dependent pages.

	What we have done is to make one Frame the "Controlling" frame.  All
actions take place in this frame.  Then, for our menu bars, title bars,
button bars, etc we create pages that are mostly JavaScript.  From the
Controlling Frame, we tell the dependent frame to create their HTML based
upon the function parameters.  (For example, each page calls
fames[x].setMenus(labels, actions), which generates the html for our menus
and then sets the innerHTML for a paticular span to the html just
generated.)  This does end up with a lot of JavaScript on the client,
however it makes the design just about as clean as a non-frame set
implementation.  It also moves some of the processing from the server out to
the client (for those worried about the load on their servers).

	Randy


-----Original Message-----
From: Jones, Stephen [mailto:sjones@rational.com]
Sent: Wednesday, February 21, 2001 12:52 PM
To: 'tomcat-user@jakarta.apache.org'
Subject: RE: best way to handle Servlets+JSPs+multiple Frames?


In our product, we use forms to POST user input data. We usually send the
input to another JSP page, but I don't see why this would not work for a
servlet's doPost(HttpServletRequest, HttpServletResponse) method.

e.g.:
	<form name="ReqAttMod" id="ReqAttMod" method="POST"
action="UserMod_Ctl.jsp" target="_top">
		<% /* form stuff here, buttons, textfields, etc */ %>
	</form>

When the servlet has made its controller-decisions, it then performs a
URL-redirect to the new HTML frameset desired (sURL), according to biz
logic, e.g.:

	response.setStatus(HttpServletResponse.SC_MOVED_TEMPORARILY);
	response.setHeader("Location", sURL);

(this is a cookie-safe redirect)

I'm sure there are other ways, as well.
Steve

-----Original Message-----
From: Sebastian Schulz [mailto:sebastian.schulz@sebastian-schulz.com]
Sent: Wednesday, February 21, 2001 10:07 AM
To: tomcat-user@jakarta.apache.org
Subject: best way to handle Servlets+JSPs+multiple Frames?


hi,

i want to develop a WebApplication
using Servlets+JSPs+JavaBeans.
(MVC)

So far no problems.

But on client-side i need a frame-based solution.
Every Frame itself is a JSP. The following i need to 
get working as smart as possible:

User-action at one Frame causes the Servlet to change
this but also all the other JSP-Frames acording to the
current action.

I know i can do this by including a JavaScript-Function
which produces a request for every Frame to the Servlet.

This sucks because of:
- i need JavaScript
- it is not smart and will lead to bad performance because of multiple, 
  redundant requests
- it is quite dangerous for some (altering) operations, which 
  shold take place only one times!

so i would be very glad, if someone have a more elegant solution!
may be there is a "best way" for this kind of problem...
thanks in advance.

bAs T.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-user-help@jakarta.apache.org

Mime
View raw message