You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Stephan Klevenz (JIRA)" <ji...@apache.org> on 2014/04/03 16:18:15 UTC

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

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

Stephan Klevenz commented on OLINGO-235:
----------------------------------------

This issue is related to V2 client code. In V2 the de-serialization doesn't distinguish between client and server use case. For client side de-serialization a validation is not required.



> 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
>
> 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)