$HTTP["host"] == "###TypeYourUrlHere###" {
var.site-root = "/var/www/###TypeYourUrlHere###/web/"
accesslog.filename = var.site-root + "../log/access.log"
alias.url = (
"/" => var.site-root,
)
# from: http://trac.symfony-project.com/wiki/lighttpd
url.rewrite-once = (
"^/(.*\..+(?!html))$" => "$0",
"^/(.*)\.(.*)" => "$0",
"^/([^.]+)$" => "/index.php/$1",
"^/$" => "/index.php"
)
# Handling dynamic content
$HTTP["url"] =~ "^/(?!js|css|images)" {
proxy-core.rewrite-request = (
"_pathinfo" => ( "^(/.*)" => "/$1" ),
"_scriptname" => ( "^/(.*)" => "/$1" )
)
}
# somthing is wrong here. this essential to get
# ajax calls /like/this/url.html working
# this is a really dirty hack
server.error-handler-404 = "index.php",
$HTTP["url"] =~ "backend\.php" {
server.error-handler-404 = "backend.php",
}
}


The most core aspect of his talk was that 5% of all latency times are produced by the business logic and all other backend stuff of your application. The other 95% (which are the ones after loading the HTML-page in the browser) are about loading images, flash files, movies, css files, javascript files as well as the interpretation of the css and the javascript.

Furthermore he recommends rules for developers how to minimíze these latency time where the user is waiting for the page beeing displayed.

The most important ones are:

• » Make Fewer HTTP Requests
• » Use a Content Delivery Network
• » Add an Expires Header
• » …the other 11

Furthermore Yahoo introduced !Yslow as a Firebug/Firefox Plugin to analyze web traffic and return recommendations for performance tuning.

Finally check this video to get more glue on it.

I was very impressed by their results and we are definitely going to test this out for our clients applications and see, if we can there add some more speed for the users accessing the pages.

• »Implementing an RSS-Feed and including it into the Auto-discovery-feature. => Tschitschereengreen RSS Feed
• »Added Microformats to our contact page
• »Got all pages with W3C conform html code.

So as we all know websites like Amazon or eBay are switching their contents displayed for every user based on information they aquired while the user was browsing the page.

So what happens, if we apply this to an Web2.0 application: The longer the user is using the web app the more “professional” look and feel he will get provided, making his clicks more precisious and bringing him faster towards the desired results. In parallel the user just registered, will see an very simple and intuitive interface guiding him through the functionality.

I’m wondering if this will work as well as it sounds or if I missed some critical aspect…

[Update] – take care that the user can influence the communication level by himself. (e.g. in Settings => display options)

Herausforderungen waren:

• Updating der benutzen MySQL-Funktionen (Kinderspiel)
• Ersatz der nicht-standardisierten MySQL-Funktionen (Limit, To_days)
• Vervollständigung von GroupBy-Klauseln und anderen Aggregatfunktionen
• Portierung der XTC DB-Struktur auf MSSQL
• Ersatz der ” aus dem phpMyAdmin-Dump durch “”
• Anpassung der Datetime-Funktionen
• Konvertierung der Datumsangaben
• Umwandeln der int() Angaben in “int”- Angaben

Als nächstes werden wir das Backend des XT ein wenig Ver-Web-Zwei-Nullen und dann die Produktpräsentation komplett mit einem AJAX-Framework neu bauen…