[jira] [Issue Comment Deleted] (OLINGO-235) Maxlength shouldn't be check when query the odata with Olingo

["Stephan Klevenz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Klevenz updated OLINGO-235:
-----------------------------------

    Comment: was deleted

(was: Hi,

Thank you for your email. I am currently out of office with limited access to my email account.

I will reply as soon as possible.

Best Regards,
Christian

)

> Maxlength shouldn't be check when query the odata with Olingo 
> --------------------------------------------------------------
>
>                 Key: OLINGO-235
>                 URL: https://issues.apache.org/jira/browse/OLINGO-235
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 1.2.0
>            Reporter: Remy Wang
>            Assignee: Stephan Klevenz
>             Fix For: V2 1.3.0
>
>         Attachments: OLINGO235-reader-option-to-switch-off-validation-of-.patch
>
>
> Hi all,
>  
> I believe in following Postel’s Law, i.e. be conservative in what you send, be liberal in what you accept.
>  
> Applying this to the Olingo client means that it should accept values longer than the server claimed to send.
>  
> This also makes sense from a project perspective as it allows the Olingo client to interact with less than perfect servers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)