[
https://issues.apache.org/jira/browse/SHINDIG-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajdeep dua updated SHINDIG-601:
--------------------------------
Attachment: fix-601-bug.patch
Made the relevant changes
Now we have 3 different converters, two ways of specifying : format and
content_type.
Also added new test cases which check for content_type related scenarios.
also updated code according to the style guidelines
> Input format detection
> ----------------------
>
> Key: SHINDIG-601
> URL: https://issues.apache.org/jira/browse/SHINDIG-601
> Project: Shindig
> Issue Type: Bug
> Components: RESTful API (Java), RESTful API (PHP)
> Reporter: Chris Chabot
> Priority: Blocker
> Attachments: fix-601-bug.patch, inputContentType.patch
>
>
> Currently PHP uses the content_type header to detect the input format. On the
> other hand Java uses the format query param (?format=foo) for the input
> format selection.
> Most logical solution seems to be that we both use :
> if ( content type is set)
> use content_type
> else if (format query param is set)
> use query param
> else
> use json
> I *think* that will be what developers would expect :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
