Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of sberyozkin@gmail.com
 designates 74.125.82.169 as permitted sender)
Message-ID: <4F737CE0.8050501@gmail.com>
Date: Wed, 28 Mar 2012 22:04:32 +0100
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: CXF Dev <dev@cxf.apache.org>
CC: Benson Margulies <bimargulies@gmail.com>
Subject: Should be JSONP interceptors moved to rt-rs-security-cors
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Benson, all,

I was wondering if it would make sense to move the JSONP interceptors to 
the CORS module.

They are in rt-rs-extension-providers (on the trunk) right now, and seem 
a bit out place there,

I'm reading CORS is a modern alternative to JSONP:

http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#CORS_relationship_to_JSONP

thus may be grouping the interceptors dealing with supporting the cross 
origin resource sharing pattern (CORS the spec related, JSONP, etc) 
would do well, we of course can do it later too

Cheers, Sergey

-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com