Hi Justin,
That makes lot of sense now :-) I'll be using cookie based authentication
and session afinity.
What I have in mind as for now is to use apache as webserver, deploy Sling
in Tomcat and connect them using ajp13 + modjk. Does this sound like a good
configuration to you? Would you have any
My appologies. By 500K child nodes, I meant that this was a root, and
that the sum of the descendants were 500K. xxx/yyy has 5 children.
Most nodes have a small number (<20) of children. Part of the testing
was to see how I needed to change the data structure so that I
minimized the number of chil
Correction - the default maximum is 200, not 1000. Not sure what I was
looking at there.
Justin
On Wed, Oct 19, 2011 at 4:18 PM, Justin Edelson
wrote:
> Phil-
> If the JSON object requested contains more than the maximum number of
> nodes, an array is returned indicating which requests can be ma
Phil-
If the JSON object requested contains more than the maximum number of
nodes, an array is returned indicating which requests can be made to
return fewer than the max number of nodes.
The typical use case for this is where /xxx contains /xxx/yy0 through
/yy9 and each of /xxx/yy0 through /xxx/y
I'm not a sling dev, but looks like the odd array gets created on a
RecursionTooDeepException [1] (line 101) then procedes to build the array on
line 125. Looking at the ResourceTraversor [2] (line 87) it iterates over
all the children, and if the count > maxResources you will get that too deep
exc
I played around in my test repository and I was able to produce that funky
array with two scenarios:
1 - if I give it a depth that doesn't exist, which doesn't seem to be your
case, that shows me an array with each element counting down from the number
I gave it to 0
2 - if the depth that I give it
I have a version of sling running that now has between 250K and 500K
nodes underneath a node called "/xxx/yyy".
When I do a get to http:///xxx/yyy/anything.1.json I get a
result that looks like:
{"jcr:primaryType":"nt:unstructured","artifact":{"jcr:primaryType":"nt:unstructured"}}
In this case
Tomcat clustering provides no value for Sling unless you are using
Sessions. Session affinity (which is really a property of the web
server / load balancer than the app server) may provide value in
certain scenarios, but this isn't dependent upon using session
clustering at the app server.
Sling's
Hi Justin,
The main goal here is to achieve high availability in case a node goes down
for any random reason. Would tomcat clustering be the recomended solution
here?
In regards to the use of Sessions, what about user authentication? How is
this information handled in Sling? is there anything to
Typically, clustering the repository is all you need. Most Sling
application do not use Sessions, but if you do you would need to
cluster Tomcat.
What specifically are you trying to accomplish?
Justin
On Wed, Oct 19, 2011 at 3:24 AM, Xavi Beumala wrote:
> Hi Justin,
>
> Thanks for the link, I f
Hi Justin,
Thanks for the link, I found it yesterday too and there's lot of info there.
I was more interested on clustering Sling though. In my case I'll be using
Tomcat, should I cluster tomcat and simply deploy sling as an app on it
configuring Jackrabbit as mentioned in the link below?
many th
11 matches
Mail list logo
