[
https://issues.apache.org/jira/browse/SLING-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640228#comment-13640228
]
Bertrand Delacretaz commented on SLING-2805:
--------------------------------------------
I haven't looked at your code in detail, but in general
for a) we generally use OSGi configs - which can always be provided as JCR
nodes via the Sling Installer
for b) I assume you need compilations and caching to happen synchronously when
a request comes in? I'd then trigger that from the services that (I assume)
your taglibs call. Eventing might be better if compile/caching is asynchronous.
What you want to avoid is compiling N times if N requests arrive
"simultaneously" on a stale cache, only one compile should happen in such a
case (which is a general caching problem).
for c) one bundle per compiled language seems to make sense - if I look at
https://github.com/bobpaulin/sling-coffee for example it's self-contained,
understandable and includes a demo and tests - I like it. Deploying is a
separate concern, the Sling Installer for example allows you to package
multiple bundles as a unit by copying them in an install folder in the
repository. As in many modular systems I think one bundle should do one thing
and one thing well - yours apparently do.
> Sling Web Resource Cache and Compiler
> -------------------------------------
>
> Key: SLING-2805
> URL: https://issues.apache.org/jira/browse/SLING-2805
> Project: Sling
> Issue Type: New Feature
> Components: Samples
> Reporter: Bob Paulin
> Priority: Minor
>
> Implemented contrib project to allow for the development web resource
> compiler plugins for languages such as CoffeeScript to compile and cache
> content on the JCR. This might make a nice addition to the contrib section.
> See implementations at
> https://github.com/bobpaulin/sling-web-resource.git
> Example implementation for CoffeeScript. Includes CoffeeScript unit tests.
> https://github.com/bobpaulin/sling-coffee.git
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
