Sorry for the very late reply here. Going over our bylaws, I think that this would require consensus approval. If that is the case, this vote failed. Am I reading this right?
On Thu, Feb 26, 2015 at 3:22 PM, Thorsten Scherler <thors...@apache.org> wrote: > On 24/02/15 10:39, Vik Tara wrote: > >> >> On 23/02/15 23:24, Thorsten Scherler wrote: >> >>> -1 >>> >>> I have to admit I am not really showing the commitment for a -1 but ... >>> >>> We have hardly discussed this vote to begin with. I heart many voice >>> quoting that we do not use lenya as it right now, me neither. However I >>> think the idea behind lenya is the awesome community behind it. >>> >>> Yes, java is not sexy anymore, yes XML hype is over, but as said by Vik >>> REST is everywhere, so why not refactor? >>> >> But is it a refactor - or a whole new application? >> >> We moved to liferay - which is full of functionality - but I have to say >> sometimes a bit heavy and full of it's own quirks. >> >> A very lean, html5 based application that incorporates a message bus to >> consume a variety of different services and output to web / mobile, now >> that would be more interesting. >> >> > In my current project we are using a cqrs architecture like the one > https://github.com/adrai/cqrs-sample of my colleague. You find many > things like https://github.com/adrai/node-eventstore and it is round up > by the use of https://www.npmjs.com/package/reflux in the front end > client. > > Everything is either a command or an event on which you - as component - > has to listen and react. We use it due to the speed of rendering over > angular and better fitting in the cqrs pattern. > > I designed some web-apps that were listing on a activeMQ queue and > dispatching the work but the pattern I am ATM applying in my work is still > much more scalable since you implement the authorization and business rule > validations in different tiers that you just need to pipe together and > decide what to send it to the bus. Anyway lenya would still be a service > responding to a various on formats but concentrate on that and only that. > Meaning basically you use the power of cocoon to transform but all the > surrounding that maybe needed to "M - Management" should be leveraged. > Concentrating on the core functions of a CMS. > > salu2 > > -- > Thorsten Scherler <thorsten.at.apache.org> > codeBusters S.L. - web based systems > <consulting, training and solutions> > http://www.codebusters.es/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org > For additional commands, e-mail: dev-h...@lenya.apache.org > >
