incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling > Higher level observation services
Date Thu, 02 May 2013 11:15:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/9/1/_/styles/combined.css?spaceKey=SLING&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Higher
level observation services</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Bertrand
    <div class="notificationGreySide">
         <p>Analyzing how we use observation in our Sling-based apps shows a number
of recurring patterns, described in this page.</p>

<p>Using JCR observation directly or Sling OSGi events does not make a big difference
in the final results, but the implementations are very different. The commit hooks provided
by <a href="" class="external-link" rel="nofollow"></a>
provide yet another way of observing content changes, which might be more efficient or scalable
in some cases.</p>

<p>Being able to express these common observation patterns as higher-level services,
if we can do that, would allow for switching the underlying implementation seamlessly, and
would also help promote best practices in how we use events, by minimizing the amount of code
to write at the application level.</p>
    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message