incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling > Observation usage patterns
Date Fri, 03 May 2013 11:35: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="">Observation
usage patterns</a></h2>
        <b>comment added</b> by              <a href="">Felix
    <div class="notificationGreySide">
       <p>Just a minor detail on impact: OSGi events are dispatched fully asynchronous
and thus don't block event processing in the repository.</p>

                <div style="border-bottom: 1px solid #ddd; padding: 10px 20px 7px 20px;">
        <strong>In reply to a comment by <a href="/confluence/display/~bdelacretaz"
                          class="url fn confluence-userlink" data-username="bdelacretaz"
                   >Bertrand Delacretaz</a>:</strong><br/>
        <p>If by "this" you mean the tentative API, then agreed, I'll remove it.</p>

<p>The interesting thing is that a number of the patterns mentioned here might not need
observation at all, a form of slow polling would work for most of them and be more scalable.</p>

<p>As you say, the Sling JcrResourceListener makes it easy to listen to specific events,
but to support that it has to blindly relay a lot of JCR events to the OSGi event queue, which
might also hinder scalability. I'll run some tests with Oak to measure what the actual impact
    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a id="reply-31820646" href="">Reply
To This</a>


View raw message