Interesting idea, especially with regards to providers. In general we really do need to improve on how providers are written and configured. We shouldn't forget about JEE either though. JEE has a lot to offer application developers that Vert.x doesn't. Not convinced we should rewrite Keycloak to run on Vert.x. Instead I'd say we should provide hooks into Vert.x and other containers (JEE) to allow users to write providers in whatever they want. The #1 thing to think about for Keycloak 2.0 IMO is customization. What parts should be customizable and how do we best allow users to do that? ----- Original Message ----- > From: "Bill Burke" <bburke(a)redhat.com&gt; > To: keycloak-dev(a)lists.jboss.org > Sent: Thursday, 8 January, 2015 1:44:01 AM > Subject: [keycloak-dev] Build on top of Vert.x? > > Don't care that much at all about AIO, but what is compelling to me > about Vert.x is that it is a polyglot platform. If our SPIs could be > written in any language and deployed easily this would be a huge win and > could potential bring together very diverse communities (node.js and > linux-python-admins). > > Something to think about for Keycloak 2.0. > > Bill > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev > _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev