[kdewebdev-webdeveloper] test

[Isaak]

Thank you Andrew, your information is very interesting and helpful.

> The reason I suggest not using AJAX is because some clients will not have 
> JavaScript enabled (Firefox NoScript plugin, or just turned off in the 
> browser).  This is done for security, and probably is a bit paranoid.  Also 
> some mobile devices do not support javascript, or have limited support.  The 
> big one is as you mentioned, search engines.

I don't really take this into account for projects as the one I am currently working on. Nowadays people should have JavaScript enabled, perhaps not globally (thank you NoScript plugin :)) but at least for the websites you give your trust to. I'm sure that every visitor who intends to visit my website will enable JavaScript in order to be able to make use of the all the features of the website.
Those who do not wish to enable JavaScript will see a clear message which explains that they have JavaScript disabled and enabling it would increase the functionality of the website, this message will also include a link to a page where instructions are explained on how to enable JavaScript in the most common webbrowsers.
And what about mobile phone visitors? Well, the website I'm currently creatiing will not be compatible with mobile phones, because it doesn't have a W at P version of the website and the width and height are way too large for mobile phones.

I would take this into account for commercial projects which needs compatibilty with all major browsers, whether they have JavaScript or images enabled or disabled, or use a different type of monitor.

> Using AJAX and XML for the sake of it is not really a good thing to do, as 
> AJAX has its limitations and overhead.  A suggestion if you wanted AJAX usage 
> would be to have your articles displayed with just a title and/or summary and 
> click the article to load via AJAX the full article.  You would probably need 
> to use PHP on the back-end to take the requests and pass back the right data, 
> or you could just load a static XML file for each article.
> An example would be the Slashdot "New" discussion format - where low rated 
> comments are not displayed until you click the title of that comment, and 
> they are loaded dynamically.
> AJAX for a static page is probably not the best use of the technology...

I couldn't agree more with your suggestion about loading certain parts of the website only when they are being activated or displayed by the visitor, but since we're only talking about news messages of a fansite this shouldn't be much of a difference so loading the complete XML file wouldn't be a problem (dispute the fact that the database would be a much better solution for this project), I only use this kind of functionality for larger projects.

PHP is much faster than JavaScript since they both are totally different scripting languages while the first one is server-side and the second one client-side. But the filesystem being much slower than the database made me choose for the AJAX solution, and using AJAX would pass most of the load to the client's computer instead of the server.

I have thought about just linking to an XML file while loading the news articles from the database and keeping the XML up to date as soon as a news is being added, but once again the reason for reducing the load on the server made me choose for AJAX. And I also thought about RSS, thanks for the suggestion though :).

One more thing:
Some may think this is way to much thinking for a small project as a fansite, but the reason for creating this website and thinking so thorough about this is because I'm increasing my experience with load balancing and use of other technologies and also increasing my knowledge about certain techniques. For a regular fansite this all this doesn't really matter but in my situation it is important ;).

Thanks a million.
---
Isaak
_________________________________________________________________
Update vandaag nog in één klik je hele online leven!
http://get.live.com