You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by UXX OData <ux...@gmail.com> on 2017/11/01 10:21:59 UTC

Regarding OData asynchronous service

Hi,

We are currently introducing Olingo asynchronous services to our code base.
While studying the source code of Olingo v4 provided in the official
website, we figured out that the way the asynchronous services are supplied
can further be enhanced.We suggest that the asynchronous service supply can
be decoupled from the processors so that we do not have to use the same set
of lines inside all the processors for calling asynchronous services.We
would like to know your opinion on this and we wish to contribute for
implementing the above mentioned functionality.We look forward to hearing
from you as early as possible.

Best regards!
UXXteam

Re: Regarding OData asynchronous service

Posted by mibo <mi...@apache.org>.
I also agree with the opinion of Ramesh, start with JIRA and a patch.
If it helps (e.g. for discussions) a committer can create an according branch for proposal (and the patch(s)).

Regards, Michael

> Am 01.11.2017 um 13:46 schrieb Ramesh Reddy <ra...@redhat.com>:
> 
> IMO if you submit a patch with test cases to show the improvement in design
> and performance then Olingo committers will be open to review. I suggest
> you start with a JIRA first [1] and detail a bit about your design. This
> may generate further discussion from where you can submit a patch for your
> proposal.
> 
> Thanks.
> 
> Ramesh..
> http://teiid.org
> 
> [1] https://issues.apache.org/jira/projects/OLINGO
> 
> On Wed, Nov 1, 2017 at 5:21 AM, UXX OData <ux...@gmail.com> wrote:
> 
>> Hi,
>> 
>> We are currently introducing Olingo asynchronous services to our code base.
>> While studying the source code of Olingo v4 provided in the official
>> website, we figured out that the way the asynchronous services are supplied
>> can further be enhanced.We suggest that the asynchronous service supply can
>> be decoupled from the processors so that we do not have to use the same set
>> of lines inside all the processors for calling asynchronous services.We
>> would like to know your opinion on this and we wish to contribute for
>> implementing the above mentioned functionality.We look forward to hearing
>> from you as early as possible.
>> 
>> Best regards!
>> UXXteam
>>

Re: Regarding OData asynchronous service

Posted by Ramesh Reddy <ra...@redhat.com>.
IMO if you submit a patch with test cases to show the improvement in design
and performance then Olingo committers will be open to review. I suggest
you start with a JIRA first [1] and detail a bit about your design. This
may generate further discussion from where you can submit a patch for your
proposal.

Thanks.

Ramesh..
http://teiid.org

[1] https://issues.apache.org/jira/projects/OLINGO

On Wed, Nov 1, 2017 at 5:21 AM, UXX OData <ux...@gmail.com> wrote:

> Hi,
>
> We are currently introducing Olingo asynchronous services to our code base.
> While studying the source code of Olingo v4 provided in the official
> website, we figured out that the way the asynchronous services are supplied
> can further be enhanced.We suggest that the asynchronous service supply can
> be decoupled from the processors so that we do not have to use the same set
> of lines inside all the processors for calling asynchronous services.We
> would like to know your opinion on this and we wish to contribute for
> implementing the above mentioned functionality.We look forward to hearing
> from you as early as possible.
>
> Best regards!
> UXXteam
>