>> You have at least three options to update "foreign" frames:
>>
>> client-side:
>> - You can use JavaScript
>> - You can use the target= parameter of <A href>'S or <FORM>'s
> <a>-links are not applicable, as they require user interaction for
> triggering the update.
So, you're looking for some kind of auto-update w/o any user
interaction ...
>> Server-side:
>> - You can use the "Window-Target:" header at the server side
>> to specify the target window of the response. (Both Mozilla
>> and IE5* support this little-known feature)
... then the server-side approach will not be usable anyway,
because Window-Target is set in the _response_ (ie. you have
to have a client-initiated request that you can respond to)
Server-side push generally scales very bad, because each
push client usually has an open connection to the server.
I remember that there is an IBM redbook with some interesting
infos on the subject. They have a nice description of all
options and their (dis-)advantages. I think it was in
"Design and Implement Servlets, JSPs, and EJBs for IBM
WebSphere Application Server".
Matthias
PS: Window-Target _may_ work too with IE4, I just haven't it.
Navigator 4.7x and probably earlier versions do support
Window-Target (which originally has been introduced from
Netscape).
