client side includes

In an earlier post Durdledoor84 asked what server side includes were. I'd
like to know about client side includes. Are there pros and cons for server
side vs. client side? Are client side includes more difficult to work with
and create?

Thanks for any input.

Fred

jandf wrote:

In an earlier post Durdledoor84 asked what server side includes were. I'd
like to know about client side includes. Are there pros and cons for server
side vs. client side? Are client side includes more difficult to work with
and create?

Ehh... what do you mean by "client side includes"?
The term doesn't exist, AFAIK, but you might call e.g. iframes and
similar for that.
If that's what you mean, the sweet thing with SSI is that the code from
the included file will merge with the page's code before it arrives to
the user which in turn means that you won't have the common issues with
iframes, i.e. scrollbars, etc.

--
Dan Vendel - *GOF*
Contact: http://www.proformica.com/en/contact.shtml
Formmail tutorial: http://www.proformica.com/en/formmail_tutorial.shtml
Nested tables: http://www.proformica.com/en/nested_table_demo.shtml
SEO: http://www.proformica.com/en/search_engine_optimization.shtml
SE Utility: http://www.proformica.com/en/advanced_web_ranking.shtml
Search Dreamweaver newsgroup: http://www.proformica.com/google.html

I guess the equivalent of a client side include is a Library Item.

--
Jules
http://www.charon.co.uk/charoncart
Charon Cart 3
Shopping Cart Extension for Dreamweaver MX/MX 2004

Julian and Dan, the following is from Builder.com:

////
What is a CSI?
A Client Side Include (CSI) is usually a short JavaScript function or
routine contained in an External JavaScript file and is called in the same
place as the SSI would be. CSIs can be contained either in a stand-alone
file or included within a global JavaScript file which contains other useful
client side JavaScript functions that the site may require.
///

I was just curious if any here had experience with CSI and if so is it
difficult to implement. I use ssi's frequently and was wondering if it's
worth learning how to use client side includes.

Thanks again.

Fred


"Julian Roberts" <newsg (AT) charon (DOT) co.uk> wrote

I guess the equivalent of a client side include is a Library Item.

--
Jules
http://www.charon.co.uk/charoncart
Charon Cart 3
Shopping Cart Extension for Dreamweaver MX/MX 2004

jandf wrote:

Julian and Dan, the following is from Builder.com:

////
What is a CSI?
A Client Side Include (CSI) is usually a short JavaScript function or
routine contained in an External JavaScript file and is called in the same
place as the SSI would be. CSIs can be contained either in a stand-alone
file or included within a global JavaScript file which contains other useful
client side JavaScript functions that the site may require.
///

I was just curious if any here had experience with CSI and if so is it
difficult to implement. I use ssi's frequently and was wondering if it's
worth learning how to use client side includes.

OK, thanks for educating me. But that can't be compared to SSI, despite
the similarity in terms. SSI includes content, CSI obviously includes
javascript functions. Two completely different things.

BTW: CSI actually means Crime Scene Investigations. I know, because I'm
unable to avoid the crappy TV series. It's all over nowadays...

--
Dan Vendel - *GOF*
Contact: http://www.proformica.com/en/contact.shtml
Formmail tutorial: http://www.proformica.com/en/formmail_tutorial.shtml
Nested tables: http://www.proformica.com/en/nested_table_demo.shtml
SEO: http://www.proformica.com/en/search_engine_optimization.shtml
SE Utility: http://www.proformica.com/en/advanced_web_ranking.shtml
Search Dreamweaver newsgroup: http://www.proformica.com/google.html

Julian Roberts wrote:

I guess the equivalent of a client side include is a Library Item.

Nope. A library item is a design time tool.


Gary

////
What is a CSI?
A Client Side Include (CSI) is usually a short JavaScript function or
routine contained in an External JavaScript file and is called in the same
place as the SSI would be. CSIs can be contained either in a stand-alone
file or included within a global JavaScript file which contains other
useful
client side JavaScript functions that the site may require.
///

That's kind of vague. Is is just a link to an external javascript file? I
think Builder.com just made up that term. ;o)

I guess the drawback with any client-side method is that you are dependant
on the client-side...which you have much less control over than you do on
the server side.

-Darrel

darrel wrote:

That's kind of vague. Is is just a link to an external javascript file? I
think Builder.com just made up that term. ;o)

That was my immediate take, too:
I use the same trick when trying to persuade clients into something they
might not approve to. I give whatever I want to do a nice acronym, and
they take for granted it's a common solution in the business.
<excerpt from Vendel's Sleazy Business Tricks>


--
Dan Vendel - *GOF*
Contact: http://www.proformica.com/en/contact.shtml
Formmail tutorial: http://www.proformica.com/en/formmail_tutorial.shtml
Nested tables: http://www.proformica.com/en/nested_table_demo.shtml
SEO: http://www.proformica.com/en/search_engine_optimization.shtml
SE Utility: http://www.proformica.com/en/advanced_web_ranking.shtml
Search Dreamweaver newsgroup: http://www.proformica.com/google.html

Didn't mean to be vague. Just wanted to illustrate that "client side
include" is a term. What I can deduce is that it uses a .js file to call any
elements into a page, like ssi. They (the famous THEY brothers) say that
it's better than ssi because it doesn't use the server to process the call
but rather the work is done by the browser hence less bandwith and faster
downloading. But the fact that you gurus don't know much about it raises red
flags to me that it isn't a recognized standard yet.

Fred



"Dan Vendel *GOF*" <see_my_signature_ (AT) _the_bottom_of_the_post (DOT) org> wrote in
message news:cg55a9$7gf$14 (AT) forums (DOT) macromedia.com...

darrel wrote:

That's kind of vague. Is is just a link to an external javascript file?
I
think Builder.com just made up that term. ;o)

That was my immediate take, too:
I use the same trick when trying to persuade clients into something they
might not approve to. I give whatever I want to do a nice acronym, and
they take for granted it's a common solution in the business.
excerpt from Vendel's Sleazy Business Tricks


--
Dan Vendel - *GOF*
Contact: http://www.proformica.com/en/contact.shtml
Formmail tutorial: http://www.proformica.com/en/formmail_tutorial.shtml
Nested tables: http://www.proformica.com/en/nested_table_demo.shtml
SEO: http://www.proformica.com/en/search_engine_optimization.shtml
SE Utility: http://www.proformica.com/en/advanced_web_ranking.shtml
Search Dreamweaver newsgroup: http://www.proformica.com/google.html

What I can deduce is that it uses a .js file to call any
elements into a page, like ssi.

something to be aware of- if it's using a document.write to put content
into the page- it will totally fail for users who have disabled JavaScript.

using a linked .js file to pull JavaScript functions into a page is good
practice. Neater code and the JavaScript is all in one file to be globally
updated. If the user has JavaScript disabled, it's no matter whether the
functions are in the head of the document or in a linked file.

using a .js file to write content into a page is a different matter.

Also- if search engines are a concern, they don't "do" JavaScript. The
"client side includes" will not be seen or executed by them- so any links or
words in them won't be traversed by the search engines.