Hi Jens, Semantic feature parity with v2 would be great for the first run. That would allow us to begin the work of removing odata4j from our code and replacing with Olingo. Also, Using the simple service implementation you have targeted for the next month will give us something to work with for v4 support.
Ideally, we would prefer to claim full support for v4 using Olingo and would like to have *something* ready late this calendar year. Thanks, Ted ----- Original Message ----- > From: "Jens Huesken" <jens.hues...@sap.com> > To: dev@olingo.apache.org > Sent: Friday, April 25, 2014 3:54:12 PM > Subject: RE: v4 Status and Roadmap > > Hi Ted, > the server implementation for V4 support is in the very beginning. I would > guess we see some first results via a basic sample service (Read) in about a > month containing: > > - Read Service Document > - Read Metadata Document > - Read Feed > - Read Entry > - Error Document > > There is no decision yet when to build a first release. > > Do you have some more details / input about what you are expecting with > regards to V4 support in the first run. Is it more a semantic feature parity > with version 2? > > Thanks for your input. > > Regards, > Jens. > > -----Original Message----- > From: Ted Jones [mailto:tejo...@redhat.com] > Sent: Freitag, 25. April 2014 20:29 > To: dev@olingo.apache.org > Subject: v4 Status and Roadmap > > > What does the timeline look for v4 support in Olingo? We are planning on > migrating to Olingo from odata4j, but would like to wait until v4 support is > available. > > Thanks, > Ted >
