Il 11/02/2014 17:19, Klevenz, Stephan ha scritto:
Hi,
I would like to start a technical discussion about a module proposal for OData
4.0 client and server library.
Starting point is that we have an OData V 3.0 client (Eduards new contribution)
and an Olingo client/server for OData 2.0. On following wiki page I did draw a
picture to get some first view on structure and to find responsibilities for
modules. The idea is to get the best out of all contributions.
https://wiki.apache.org/Olingo/Olingo%20Module%20Proposal
There is not so much explained. Feel free to ask, comment or discuss.
Greetings,
Stephan
Hi Stephan, I'm taking a look at the wiki page "Olingo Module Proposal".
I've just a consideration to point out.
OData V 3.0 client is composed of two main modules: the engine and the
proxy.
These are two difference abstraction layers with different scopes, of
course.
The engine is the low-level communication layer taking care of actual
REST communication and OData entity (de)serialization, exposing methods
to hook into the OData protocol for manipulating entities and invoking
actions and functions. It is there for Java developers that needs to
access underlying details of the OData communication protocol.
The proxy converts any local change to POJOs and any local invocation of
annotated interfaces' methods into actual calls to the Engine layer. It
is thought for experienced Java developers which are familiar with
widespread Java Enterprise and / or Open Source technologies and prefer
to interact with OData services at a very abstract level (like JPA, more
or less).
Of course, the proxy layer depends on the engine layer BTW each one can
be considered as a different client.
May be it would be better to explain this concept into the picture. What
do you think?
Best regards,
F.
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
