Hello,

A simple question: what gives more overhead to a server, Iframes or Includes (ssi)?

ssi, as iframes don't have overheads.

Okay thank you. I do not know how to formulate these things right. Let me try again:

What of SSI or Iframe takes more server resources?

Sorry, I wasn't being pedantic. Iframes don't use up server resources or have overheads - they are just html tags. SSI actually uses up lots of resources because the server needs to do lots of processing. .

Okay, so if you can do the same thing with both, it's better to use iframe then. Thank you

Not necessarily, as it is client dependent (you'll need to use ilayer for older versions of Netscape). Using SSI is server dependent and thus is client independent, which means in terms of cross-system compatiblity, it's best to use server side solutions, than client-based ones.
========================================
Buh Bye!

Cheers,
Me

Older versions of netscape? How old, prior to netscape6 ?

I beleive it is anything before v6.

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!

Okay thank you everybody.

4.x (and before) and 6.1 (I believe that with the DOM transfer had not properly occurred in early betas of 6.X).
========================================
Buh Bye!

Cheers,
Me

What do you mean? Sorry but I do not get it.

What I _mean is that you will have to use ILAYER codes to accomodate ALL netscape browsers, except for NS6.2 and above.

Thus, IFRAME is NOT supported in NS 6.1 and below.

And my point...use server-side solutions that are NOT client-dependent.
========================================
Buh Bye!

Cheers,
Me

I'm not sure if iFrames are really faster, they may produce even more overhead.

Assuming all you're trying to do is include one file into another, iframes will require two requests. One for the main page and another one for the iframe content. Under bad conditions, your iframe conte delivery may be delayed or may not render due to a dropped request. Still, if they're generally static pages, I don't think it really matters so much as what makes the html easier to maintain.

Ahh... that's right. browser implementations.

SSI is a much nicer way to go

I think sourceforge.net use IFrames for their banners and the rest of the page won't load until the iframe loads and it can sometimes take ages...I don't like that :(

how about php?

Honestly to speak I've never bothered with IFrames since at the time I was on a php kick.

---

openoffice + gimp + sketch ...

Same thing as SSI with the include function.
========================================
Buh Bye!

Cheers,
Me