| muaddib on Dec 20, 2000 at 1:10:32 PM | Rating: 3 |
| austegard on Dec 8, 2000 at 7:04:54 AM | Rating: 3 |
| Neat. But why not just take the step up to PHP? Most reasonable Unix hosting plans offer either version 3 or 4 for free, and it is easier (and infinitely more powerful and expandable) than XSSI seems to be. |
| bigerv on Dec 4, 2000 at 5:31:26 AM | No Rating |
SSI is Server Side (hence it's based on the server)
JavaScript(for 99.8% of the time that you'll use it) is Client Side(or Browser based)
The nice thing about doing things server side is that you know exactly what content is being sent to the client. That way you don't have to put the load on the client's machine to render a page with multiple platform specfic javascripts and style sheets on a singles page.
(If I'm rambling its because its a Monday) |
| matjday on Dec 4, 2000 at 1:20:33 AM | No Rating |
|
nakhtar
Access is great for just the situation you describe: running a small, simple site which won't get a high hit-rate. While access doesn't have the performance of SQL Server we've often found it to be the best option for small intranet applications where you don't need the power and complexity of full blown SQL Server.
Cheers
Mat |
| nakhtar on Dec 1, 2000 at 6:09:49 AM | No Rating |
Using Access database for the website.
Does anybody has any experience using Access database for a website. How does it perform for simple sql queries, insertions and updates. |
| zpeef on Nov 30, 2000 at 12:18:31 AM | Rating: 5 |
One question... does SSI work on freesites?
I saw on one page that your server had to have a *.txt file containing something for it to work... |
| matjday on Nov 20, 2000 at 2:29:40 AM | No Rating |
dzelber
Yep, you're on the right track. SSI is server-side so (among other things) it enables you to send different versions of a page to different user agents. This is a fundamentally different approach to sending one meta-page to all JavaScript-enabled agents and using forks to write the correct HTML / call the right methods.
We are using SSI to dymanically build pages at request-time.The "core page" itself is a very basic HTML page which "includes" site-wide and "section-wide" header and footer files that contain the more complicated code which applies the site look and feel.
This allows our Web editors to work with very simple pages, so they can concentrate on the content. While we are able to update the look of the whole site just by editing a few include files. We are also able to send different versions of a page to different UAs by using conditional includes to add different header and footer files to the HTML 3.2 compliant "core page".
Cheers
Mat |
| dzelber on Nov 19, 2000 at 6:35:16 AM | No Rating |
Well,
So far, nothing better than simple JavaScript (as in the example above...). My question would be: what makes this code running? is it browser dependent or is it up to your web server (Apache, IIS...)?
The only advantage I can find for that is if this code is web-server dependent and not browser dependent. If so, it could run on types of browsers that do not support JavaScript and thus one can't find out important stuff about the browsers...
For instance: the AvantGo browser (for PDAs) does not support JavaScript. It runs only HTML 3.2!
Could any body shade some light on this? |
| pimpyt on Nov 13, 2000 at 12:38:49 AM | Rating: 4 |
I've been doing this for years, with JavaScripts and with ASP lately, works for CSS to, like this:
<script LANGUAGE="JavaScript">
browser_name = navigator.appName;
if (browser_name == "Netscape")
{
document.write('<link REL="stylesheet" TYPE="text/css" HREF="./css/nn.css">');
}
if (browser_name == "Microsoft Internet Explorer")
{
document.write('<link REL="stylesheet" TYPE="text/css" HREF="./css/ie.css">');
}
else document.write('<link REL="stylesheet" TYPE="text/css" HREF="./css/nn.css">');
</script> |
| beyer on Nov 12, 2000 at 5:55:36 AM | Rating: 4 |
In IIS you can use, I ASP:
<% if InStr(Request.ServerVariables("HTTP_USER_AGENT"), "MSIE") > 0 then %>
<!--#include file="iebar.htm" -->
<% else %>
<!--#include file="defaultbar.htm" -->
<% end if %>
Note that IIS first load all include files an control i.e. declaration and report i.e. repeated declarations as errors, then it use the conditions to select which include will be active. |
| matjday on Nov 10, 2000 at 12:53:14 AM | No Rating |
|
Friedle
I'm assuming you read my comment and also MS's docs re SSI on IIS:
http://msdn.microsoft.com/library/partbook/asptech/includingcontentsofdiskfile.htm
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/iisref/serv24bp.htm
Can you outline the problem you are having (e.g. which bits of SSI work and which don't)? - someone on this site should be able to help you out.
Cheers
Mat |
| Friedli on Nov 9, 2000 at 11:59:04 PM | Rating: 5 |
| That's what I was looking for. But, does anybody have an idea if that works on IIS4.0 as well? I couldn't make it running |
| matjday on Nov 8, 2000 at 2:22:28 AM | Rating: 4 |
|
A useful introduction to a powerful technology - especially the use of regular expressions (the number of JavaScripters who write long, convoluted string parsing code when regexp would do the job in a single expression is frightening).
The writer omits to give any further reading - so here are a couple more intros to SSI:
http://www.apacheweek.com/features/ssi
http://www.bignosebird.com/sdocs/extend.shtml
http://www.bignosebird.com/sdocs/browser.shtml
SSI on IIS:
By default a page must be named *.asp for the server to parse it for server side code. At first glance IIS doesn't seem to support XSSI but you can do basic SSI includes etc, see e.g.:
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/iisref/iiwainc.htm
My thought is that you might need to use server side JScript (or VBScript) to emulate this behaviour.
(MS bunnies - any input on this?)
Cheers
Mat |
