Custom IO policies for plugins.

[Vladimir Ozerov]

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.

[yzhdanov]

+1 You definitely should file a ticket.

--Yakov

2015-06-26 13:05 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> 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.
>

[Vladimir Ozerov]

I created a ticket: IGNITE-1058.

On Fri, Jun 26, 2015 at 3:50 PM, Yakov Zhdanov <[hidden email]> wrote:

> +1 You definitely should file a ticket.
>
> --Yakov
>
> 2015-06-26 13:05 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > 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.
> >
>