Re: oak-resilience

Plus some ideas what Aurora DB from AWS uses for resilience testing: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Managing.html#Aurora.Managing.FaultInjectionQueries On 08/03/16 11:19, "Michael Dürig" wrote: > >+= out of file descriptors > >Michael > >On

Re: OAK-3884 for UDBBroadcaster

tion. >The Serverfault question referenced in the Oak issue was about broadcasting >to the loopback address, which can't be done. >The patch looked like it was attempting to do that. > >Best Regards >Ian > > >On 14 January 2016 at 20:48, Philipp Suter <su...@adob

OAK-3884 for UDBBroadcaster

Hi I added a small patch to https://issues.apache.org/jira/browse/OAK-3884 that could fix the broadcast unit tests for UDBBroadcaster. It seems the loopback interface is not allowing broadcasting on *NIX systems. The broadcasting IP has to be found dynamically for a test execution.

Re: OAK-3884 for UDBBroadcaster

t will be >directed at the .127 host on the /24 subnet. (I haven't tried to see what >a switch does with 2 overlapping and misconfigured subnets.). > > > >HTH >Best Regards >Ian > > > > > >On 14 January 2016 at 17:30, Philipp Suter <su...@adobe.com> wrote: &g

Re: Release dates

Actual release data would be great to map planing dependencies properly. On 13/08/15 13:58, Davide Giannella dav...@apache.org wrote: On 13/08/2015 10:17, Stefan Egli wrote: I¹d find it more useful (for us) when it would be the cut-date. It's always the cut date in the beginning. Shall we

Re: Modularization

I took some inspiration from Apache Aries for this hierarchical maven structure. It has very fine granular OSGi modules (not that we have to do that too) and still keeps everything in one hierarchical Maven project. With a hierarchical maven project structure you can build/ test/ install

Re: Modularization

On 06/08/15 13:36, Davide Giannella dav...@apache.org wrote: Grouping two emails together On 06/08/2015 12:04, Michael Dürig wrote: I neither like Sling's constantly moving towards smaller and more specific modules as too me this seems to be mostly driven by OSGi as a technology and not by

Re: Modularization

Ideally you have a “root” project, e.g. /oak /security /api /implementationA /implementationB /core /persistence /.. Apache Aries has for example a pretty nicely structured hierarchical Maven set-up. You can still build all of it starting on top.. In the end smaller

(OAK-2416) Support continuable sessions

Hi I had an offline discussion with Francesco regarding the implementation of the revision for the continuable session in the OAK API and read through the comments in [1]. Some additional comments to what Alex mentioned yesterday: I like the idea of separating the internal revision from the