You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Vladimir Ozerov <vo...@gridgain.com> on 2015/06/26 12:05:10 UTC
Custom IO policies for plugins.
Igniters,
Currently we have enum GridIoPolicy which defines thread pool that must
process a message on remote node.
There is a chance that extension developers will require to process
messages in their specific pools. For now it is not possible.
How about changing GridIoPolicy to a set of byte constants so that plugins
can register their own policies? This will not break backward compatibiliy
as we alraedy write policy as byte, and will only require some
starightforward refactoring.
Vladimir.
Re: Custom IO policies for plugins.
Posted by Vladimir Ozerov <vo...@gridgain.com>.
I created a ticket: IGNITE-1058.
On Fri, Jun 26, 2015 at 3:50 PM, Yakov Zhdanov <yz...@apache.org> wrote:
> +1 You definitely should file a ticket.
>
> --Yakov
>
> 2015-06-26 13:05 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
>
> > Igniters,
> >
> > Currently we have enum GridIoPolicy which defines thread pool that must
> > process a message on remote node.
> > There is a chance that extension developers will require to process
> > messages in their specific pools. For now it is not possible.
> >
> > How about changing GridIoPolicy to a set of byte constants so that
> plugins
> > can register their own policies? This will not break backward
> compatibiliy
> > as we alraedy write policy as byte, and will only require some
> > starightforward refactoring.
> >
> > Vladimir.
> >
>
Re: Custom IO policies for plugins.
Posted by Yakov Zhdanov <yz...@apache.org>.
+1 You definitely should file a ticket.
--Yakov
2015-06-26 13:05 GMT+03:00 Vladimir Ozerov <vo...@gridgain.com>:
> Igniters,
>
> Currently we have enum GridIoPolicy which defines thread pool that must
> process a message on remote node.
> There is a chance that extension developers will require to process
> messages in their specific pools. For now it is not possible.
>
> How about changing GridIoPolicy to a set of byte constants so that plugins
> can register their own policies? This will not break backward compatibiliy
> as we alraedy write policy as byte, and will only require some
> starightforward refactoring.
>
> Vladimir.
>