avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharmarke Aden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1213) Dependency on Jetty Servlet API in IPC
Date Fri, 30 Nov 2012 22:23:58 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507712#comment-13507712
] 

Sharmarke Aden commented on AVRO-1213:
--------------------------------------

Doug,

I wasn't really sure in what capacity Jetty is used but looking at IPC code it looks like
those jetty dependencies are needed down stream by those wishing to use IPC. 


Scott, 

I think you are right on them money. Ultimately what you want to do is break the IPC into
Jetty and Netty sub-modules so they can become optional and allow of future growth with respect
to adding new Server implementations (i.e. tomcat, vert.x, NodeJS, etc).
                
> Dependency on Jetty Servlet API in IPC
> --------------------------------------
>
>                 Key: AVRO-1213
>                 URL: https://issues.apache.org/jira/browse/AVRO-1213
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.2
>            Reporter: Sharmarke Aden
>            Priority: Minor
>
> The compile scoped dependency on jetty servlet-api in the IPC pom file can be problematic
if using Avro in a webapp environment. Would it be possible to make this dependency either
optional or provided? Or maybe Avro modularize into sub-modules in such a way that desired
features can be assembled piecemeal?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message