Re: [Rdfapi-php-interest] RAP use case: vod.sch.gr

[Chris B. <ch...@bi...>]

Hello Vangelis,

nice to hear that you like RAP.

I think a caching layer would also be useful for many other projects based 
on RAP.
What do you think about contributing it to the RAP code base?

Christian Weiske <cw...@cw...> is currently work on the RAP SPARQL 
engine. If you like to contribute your code, please send it to the list so 
that Christian can see how it fits together with his developments.

Cheers

Chris

--
Dr. Chris Bizer
Freie Universität Berlin
+49 30 838 54057
ch...@bi...
www.bizer.de

----- Original Message ----- 
From: "Vangelis Haniotakis" <han...@uc...>
To: <ch...@bi...>
Sent: Sunday, April 15, 2007 4:15 PM
Subject: RAP use case: vod.sch.gr


> Hello.
>
> We thought you'd appreciate knowing that we're currently using
> RAP 0.9.4 in production as the backend for the Greek School
> Network Video on Demand website. It's a fairly trivial use
> case, but here goes:
>
> We have a small amount of RDF/Dublin Core metadata about our videos
> (about 5000 records at the moment). We used to store these in
> an XML database (eXist) and access them with XQuery, but we decided
> to go with SPARQL for the next iteration of development.
>
> We're using PHP for the front-end, heavily utilizing the Prado
> framework as well as AJAX technologies. We rely on data from RAP
> for pretty much all the information displayed on the website, using
> previously prepared SPARQL queries.
>
> Since in the course of a single page / AJAX request we ended up doing
> a good amount of RAP calls, in the interests of performance we interjected
> a caching layer between our frontend and RAP. Fairly simple: we md5()
> the query and save the serialized results to a database. On next
> call, we md5() the query again, pull the results from the cache DB,
> and never hit RAP at all. In this way we can have a quite responsive
> webpage with small performance hits when a cache entry expires.
>
> You can see the website here:
> http://vod.sch.gr/
>
> We'd like to sincerely thank the RAP development team for their effort
> and quality code; you made our job significantly easier.
>
>