[
https://issues.apache.org/jira/browse/OLINGO-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833906#comment-13833906
]
Stephan Klevenz commented on OLINGO-72:
---------------------------------------
try this:
git clone https://git-wip-us.apache.org/repos/asf/incubator-olingo-odata2
And have also a look here:
https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=blob;f=odata2-lib/odata-ref/src/main/java/org/apache/olingo/odata2/ref/processor/ListsProcessor.java;h=3238293baca6f9d59443107932c6f9faf5d5474c;hb=038f49e911eb3aced118e9bf0fdaedfa095a2fea
Line 165, readEntitySet() has implemented server side paging (limited to 100
entries per feed).
> Processor interceptor and data stream
> -------------------------------------
>
> Key: OLINGO-72
> URL: https://issues.apache.org/jira/browse/OLINGO-72
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 1.1.0
> Reporter: Eugenio Lentini
>
> Good morning,
> I have two questions/improvements for olingo:
> 1) a sort of processor interceptor for authorization: for the time being I
> have implemented a processor in order to perform the authorization of my
> odata service.
> Some clients, such as MS-Excel, want a specific answer in order to send
> user:pass so I have put this response with error 401 inside of a processor
> which is created by the Factory. Once the client has sent the credentials I
> can instantiate, always inside of the factory, the processor to build the
> atom feed.
> 2) stream data to the client: I have a lot of data, may be big data, and I
> cannot load all of them in memory for the conversion so it would be great to
> have a way to have access to the response object, or another way, to stream
> data to the client and not in one shot.
> If it is already possible could you please suggest the method or document it?
> In case I could even send you a working example to save up your time.
> Thanks a lot for the attention and the work you are doing.
> Eugenio
--
This message was sent by Atlassian JIRA
(v6.1#6144)
