Using Frames

[Chris Kelleher]

I am looking into using frames in my HTML coding. First, are frames worth
implementing with webspeed? Second I was wondering if something like the
following would be the correct way to implement frames using webspeed:

<BLOCKQUOTE><font size="1" face="Arial, Verdana">code:</font><HR><pre>
&lt;html&gt;
&lt;head&gt;&lt;/head&gt;
&lt;frameset COLS="50%,*"&gt;
&lt;frame SRC="/scripts/cgiip.exe/wservice=servicename/first.html&gt;
&lt;/frame&gt;
&lt;frame SRC="/scripts/cgiip.exe/wservice=servicename/second.html&gt;
&lt;/frame&gt;
&lt;/frameset&gt;
&lt;/html&gt;
[/code]

I seems like this approach would fire off a series of webspeed objects that
would generate the htmls required for the whole frameset.

Roland Schaer
Senior Programmer/Analyst
RAM Software Systems, Inc.
Roland.Schaer@ramsys.com
972-669-0763

 

[Chris Kelleher]

Frames are very useful in webspeed. One popular use is to keep one small
frame open at all time with site navigation and display pages on the
remaining frame. I like to do something called the hidden frame submit. This
is where all the user sees is a single frame, but the is a "hidden" 0 pixel
high frame which does all the postings. So the page the user sees never
posts yet data is sent back and forth to the database. One word of warning
though, if you get carried away and have several frames per page, each frame
will require an agent. So if you have five agents and your main page has
four frames and two people try to log in at the same time, you will have
problems with individual frames having no agents available.

Mario

 

[Chris Kelleher]

Using HTML Frames really has nothing to do with WS. It's
more related to your application design and whether or not
that design could benefit from such an approach.

Yes, you can do this. You aren't required to run a WS
WebObject to load each frame though. That all depends
on your application. I would name each frame above so
that referencing them from your HTML has more meaning.

Yes, your above example would cause the browser to
send two web requests to the web server. Since they
are both WS requests, it's very possible that a separate
WS Agent will service each request simultaneously.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R o b e r t J. M i r r o
rmirro@microserve.net http://www.microserve.net/~rmirro/

I have lost the will to live
Simply nothing more to give
There is nothing more for me
Need the end to set me free
- Metallica
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Chris Kelleher]

I'd just like to clarify this a bit. It's not guaranteed
that each frame will require an agent. If you are initially
defining (loading) an HMTL Frameset, it's very possible that
a WS Agent will be needed to service each web request to load
each frame. That depends on how long each request takes to
load each frame. If each web request is quick, it's very
possible that one agent may be used to load multiple frames.

Also, once the Frameset is defined, you're application design
will dictated how many frames are loaded per web request. There
are ways to minimize web requests by using JS to write HTML
to frames (as opposed to invoking a WS WO to do so).

Again, this really depends on your application.


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R o b e r t J. M i r r o
rmirro@microserve.net http://www.microserve.net/~rmirro/

I have lost the will to live
Simply nothing more to give
There is nothing more for me
Need the end to set me free
- Metallica
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~