On Sep 13, 2011, at 12:24 PM, Sanne Grinovero wrote:
> On 13 September 2011 11:25, Galder Zamarreño wrote:
>>
>> On Sep 12, 2011, at 1:32 PM, Sanne Grinovero wrote:
>>
>>> I've added a new table as suggested by Galder, and sent a pull request
>>> to constrain Query in the range I just defined
On 13 September 2011 11:25, Galder Zamarreño wrote:
>
> On Sep 12, 2011, at 1:32 PM, Sanne Grinovero wrote:
>
>> I've added a new table as suggested by Galder, and sent a pull request
>> to constrain Query in the range I just defined [1]
>>
>> For this case we only have a single byte to share acro
On Sep 12, 2011, at 1:32 PM, Sanne Grinovero wrote:
> I've added a new table as suggested by Galder, and sent a pull request
> to constrain Query in the range I just defined [1]
>
> For this case we only have a single byte to share across all commands.
> Is it reasonable to reserve 100 values fo
I've added a new table as suggested by Galder, and sent a pull request
to constrain Query in the range I just defined [1]
For this case we only have a single byte to share across all commands.
Is it reasonable to reserve 100 values for Infinispan core, and blocks
of 20 for needing modules?
1 - ht
On Sep 8, 2011, at 2:05 AM, Sanne Grinovero wrote:
> Hi all,
> I've just updated the table at the bottom of
> https://docs.jboss.org/author/display/ISPN/Plugging+Infinispan+With+User+Defined+Externalizers
>
> to reserve a range for usage of custom externalizers in Hibernate Search.
>
> I'm also
Hi all,
I've just updated the table at the bottom of
https://docs.jboss.org/author/display/ISPN/Plugging+Infinispan+With+User+Defined+Externalizers
to reserve a range for usage of custom externalizers in Hibernate Search.
I'm also going to need custom commands; do we need to similarly
reserve ran
