![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
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 |
#12
| |||
| |||
|
#13
| |||
| |||
|
|
Didn't mean to be vague. Just wanted to illustrate that "client side include" is a term. |
|
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. |
#14
| |||
| |||
|
|
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. |
#15
| |||
| |||
|
|
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. Hmm..."client side include" returns 691 hits on google. "server side include" returns 53,000 I did find the article you might be referring to: http://builder.com.com/5100-6371-5172019.html The 'benefits' the article touts are mainly theoretical...hardly measurable in most cases. And they gloss over the main con...that it's entirely dependant on javascript. I'd say that CSI is mildly interesting for a read, but rather impractical and offers no real value and some real drawbacks compared to SSI. The author uses his own site as an example of CSI: http://www.greggriffiths.org/ Turn off javascript and try navigating through the site...not terribly convenient. -Darrel |
#16
| |||
| |||
|
|
Client Side Include is simple, it's what that OTHER page maker (FrontPage) uses. "Gary White" <reply (AT) newsgroup (DOT) please> wrote in message news:2m4ci01bjiuk49hn7dl724f9mesdsmk40g (AT) 4ax (DOT) com... 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |