Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: neutral (herse.apache.org: 210.54.141.241 is neither permitted
 nor denied by domain of rahul.thakur.xdev@gmail.com)
Message-ID: <45B7E04D.5000104@gmail.com>
Date: Thu, 25 Jan 2007 11:40:13 +1300
From: Rahul Thakur <rahul.thakur.xdev@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: continuum-dev@maven.apache.org
Subject: Re: [vote] merge id-refactor branch changes
References: <45B5349B.9020707@gmail.com> <45B6FBAD.9060203@apache.org>
 <000501c73f8e$7528e9f0$4001a8c0@nonec03d6244ff> <45B74692.8010907@apache.org>
In-Reply-To: <45B74692.8010907@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


Trygve Laugst�l wrote:
> Rahul Thakur wrote:
>>>> 'int' ids are now converted to 'long' across the project and to 
>>>> allow really large values. This should cater to scenarios where the 
>>>> id generation could be started from an arbitrary large value.
>>>
>>> Won't this break the API?
>>
>> Yep, it would.
>>
>>>
>>> What is the use case where 4 billion IDs isn't sufficient?
>>
>> 2 billion you mean :-). But this also more of something that I have 
>> noticed  'traditionally' that ids are specified as long and stored as 
>> bigints in database
>
> No, 4 billion. an int is +-2billion. Anyway, just because longs are 
> more traditionally used that is not a good enough reason to switch to 
> longs and break the API to me.

Yep, I know, I was referring to the +ve 2 billions. I could say a case 
where Id generation could be set to start from a fairly large value and 
so are the Id sequence increments. One could argue this is an edge case 
;-).

IMHO the version change to 1.1 is a fair indication that the API might 
have changed. Having said that, I will go with whatever most of us think 
sounds practical :-)

Cheers,
Rahul

>
> -- 
> Trygve
>