Merging this into 2.0 would allow us to benchmark the performance of this new 2.0 stuff as well. I'd be excited to see if there is a notable improvement. On Mar 25, 2014, at 8:28 AM, Rod Simpson <[email protected]> wrote:
+1 on going to 2.0 instead of master -- Rod Simpson @rockerston rodsimpson.com On March 25, 2014 at 9:19:47 AM, David Johnson (JIRA) ([email protected]) wrote: [ https://issues.apache.org/jira/browse/USERGRID-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946661#comment-13946661] David Johnson commented on USERGRID-103: ---------------------------------------- I'm still working on getting my build to work, and reviewing the code. One issue I would like to discuss is, where should we merge this change? I think the extensive code changes and could be destabilizing and would prefer to see the Usergrid master stay pretty stable, something we can release real soon. I would vote for merging this code into the two-dot-o branch instead. Thoughts? Upgrade to JAX-RS 2.0 (jersey 2.x) ---------------------------------- Key: USERGRID-103 URL: https://issues.apache.org/jira/browse/USERGRID-103 Project: Usergrid Issue Type: Improvement Components: Stack Reporter: Strong Liu JAX-RS 2.0 brings lots of new features, much better extensible and async support are ones I think most useful -- This message was sent by Atlassian JIRA (v6.2#6252)
