raja PROXY is a resource cache manager for express-dom.

Plugins are resources, and resources are proxied, proxies send messages, and raja links the messages to resources using stored relations by plugins, the plugins are asked to refresh the resources and the stored relations, recursively.

- databases, static files, external sources, html models are all resources
- express-dom plugins can build resources
- all resources have proxies that can send synchronisation messages
- messages are dispatched to plugins handling the resource depending on the modified resource
- the plugins rebuild resources as needed


raja with the http cache is at the heart of the website, and no configuration!

Whether for SEO optimization issues of sustainability of the site, performance or compatibility between browsers, you need an implementation isomorphic to generate web pages on the client and on the server?

You want to use the DOM and JS to build your web pages?

Whether on the client or on the server, generating a page edited by JS on the DOM is too slow and resource hungry?

You want to manage the cache the generated pages?

raja offers effective management, rigorous and relevant to the validity of all components.
raja control the environment of the web page on the server to know ALL the dependencies used and monitor their validity.
raja cover each of the following dependencies used and their validity, that your resources are local or remote.

raja has a granular and efficient management of the cache, a distributed cache and synchronized.

If the page is modified between the time it is sent and the time it is opened by the customer, it may have been invalidated.
The distributed cache raja synchronizes any invalidations between the two states.

express-dom is the DOM for raja, is based on WebKitGTK, faster than jsdom.

When a plugin builds a resource, it must list the url(s) used to build it. It must pass raja what url(s) was (put/post/delete) and for each url provide the list of urls it had to fetch to build them.

raja hooks into express-dom and express to handle the caching of resources/pages based on how the cache is valid for a given url.

When a backend resource is modified, the same thing happens except that it often doesn't depend on any url, it just produces one out of nothing raja has to know, a file, a db, an external source tracked differently.

When a page is loaded out of an html file on disk, we can off-load the task of tracking that file changes to a "file resource" that will take care of notifying when the file changes - raja will call the appropriate plugin. Note: multiple plugins can produce the same URL. They are chained in the order they were called.

Connexion utilisateurs enregistrés

We noticed some issues

Connexion par réseaux sociaux :

Contact us :

EDA s.a.r.l.
La grande Roulière
79150 Voultegon
France

info@eda.sarl
+(33) 607 182 560