incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling > Supporting CRUD
Date Sun, 08 Jul 2012 16:54: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="">Supporting
        <b>comment added</b> by              <a href="">Dragos
Dascalita Haut</a>
    <div class="notificationGreySide">
       <p>Regarding ResourceProviders: having a CDNResourceProvider or even simpler,
a FileSystemResourceProvider, in which case some metadatas about the files are stored in JCR,
while the actual file is stored on a network disk, separate from the JCR data store, how would
we reflect this in the ResourceProvider ? By path only ? Can we also have something similar
to "jcr:resourceType",  but with a slightly different name, maybe "sling:resourceProvider"
? I think that this would make it easier to attach additional resource providers to existing
JCR nodes. </p>

<p>Or, saying that JCR shouldn't be more important that other resource providers, are
there any plan to surface out some quick info about what the content of a Node is ? Maybe
in a shape of metadata ? I'm asking this as I'm thinking how would we perform search queries
on nodes, having multiple resource providers in some of the children ?</p>

    <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-29130823" href="">Reply
To This</a>


View raw message