On 1/24/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi Michael,
Michael Heuer wrote on Friday, January 20, 2006 7:40 PM:
On Fri, 20 Jan 2006, Phil Steitz wrote:
I have started working on this. What I had in mind was just a simple
facility for creating composite identifiers created by
On Fri, 20 Jan 2006, Phil Steitz wrote:
On 1/17/06, J?rg Schaible [EMAIL PROTECTED] wrote:
Stephen Colebourne wrote on Monday, January 16, 2006 11:13 PM:
J?rg Schaible wrote:
The release plan is available now:
http://wiki.apache.org/jakarta-commons/id/1.0ReleasePlan
Looks good,
Hi Michael,
Michael Heuer wrote on Friday, January 20, 2006 7:40 PM:
On Fri, 20 Jan 2006, Phil Steitz wrote:
I have started working on this. What I had in mind was just a simple
facility for creating composite identifiers created by concatenating
results of an array of generators. This
On 1/17/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Stephen Colebourne wrote on Monday, January 16, 2006 11:13 PM:
Jörg Schaible wrote:
The release plan is available now:
http://wiki.apache.org/jakarta-commons/id/1.0ReleasePlan
Looks good, though we may actually want to keep
Hi Phil,
Phil Steitz wrote:
On 1/17/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Stephen Colebourne wrote on Monday, January 16, 2006 11:13 PM:
Jörg Schaible wrote:
The release plan is available now:
http://wiki.apache.org/jakarta-commons/id/1.0ReleasePlan
Looks good, though we may
Stephen Colebourne wrote on Monday, January 16, 2006 11:13 PM:
Jörg Schaible wrote:
The release plan is available now:
http://wiki.apache.org/jakarta-commons/id/1.0ReleasePlan
Refactor PrefixXXXGeneratorIdentifier implementations
This should be done with great care. id generation is very
Hi Phil,
Phil Steitz wrote on Monday, January 16, 2006 1:31 AM:
On 1/15/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Phil Steitz wrote:
On 1/14/06, Michael Heuer [EMAIL PROTECTED] wrote:
Jörg Schaible wrote:
8/ Prefix generators
We have 3 generators, that add a prefix to the
Hi Phil,
Phil Steitz wrote on Monday, January 16, 2006 1:27 AM:
[snip]
I know quite some projects that use a snapshot of c-id
to generate UUIDs in production (including some of mine).
I don't know what we can do to make it more clear that people should
*not* depend on code in the commons
Hi fellows,
Jörg Schaible wrote:
Phil Steitz wrote on Monday, January 16, 2006 1:27 AM:
[snip]
In any case, I think we have critical mass to get [id] promoted and
released, and the API decisions left to make are fairly simple, so we
should agree on a release plan and get the work done.
Jörg Schaible wrote:
The release plan is available now:
http://wiki.apache.org/jakarta-commons/id/1.0ReleasePlan
Refactor PrefixXXXGeneratorIdentifier implementations
This should be done with great care. id generation is very performance
and sync sensitive in many systems.
Introduce a
Phil Steitz wrote:
On 1/14/06, Michael Heuer [EMAIL PROTECTED] wrote:
Jörg Schaible wrote:
8/ Prefix generators
We have 3 generators, that add a prefix to the generated id. All 3
classes to mainly the same for 3 different StringIdentifierGenerators.
Proposal: Since we have a lot
Hi Phil,
Phil Steitz wrote:
snip/
For me the question is, does a normal user really care about the
specifics of an unique id. The most difference is the returned type of
the id, because that may impact other parts of the code (e.g. DB).
I think many apps will care about more than just
On 1/15/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi Phil,
Phil Steitz wrote:
snip/
For me the question is, does a normal user really care about the
specifics of an unique id. The most difference is the returned type of
the id, because that may impact other parts of the code (e.g.
On 1/15/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Phil Steitz wrote:
On 1/14/06, Michael Heuer [EMAIL PROTECTED] wrote:
Jörg Schaible wrote:
8/ Prefix generators
We have 3 generators, that add a prefix to the generated id. All 3
classes to mainly the same for 3 different
Hi folks,
reviewing c-id I found more issues to resolve before releasing 1.0 final.
Since I already reported different complaints, I create here a summary of
anything already reported and all new issues.
1/ Concept of IdentifierGeneratorFactory
The IdentifierGeneratorFactory provides a
Good summary, comments inline...
--- Jörg Schaible [EMAIL PROTECTED] wrote:
4/ Copied c-codec classes in official API
To remove a dependency to c-codec the digest and hex utilities have been
copied to c-id, but they are now publicly available in the o.a.c.id
namespace.
Martin already
Hi Tim,
Tim OBrien wrote:
Good summary, comments inline...
--- Jörg Schaible [EMAIL PROTECTED] wrote:
4/ Copied c-codec classes in official API
To remove a dependency to c-codec the digest and hex utilities have been
copied to c-id, but they are now publicly available in the o.a.c.id
--- Jörg Schaible [EMAIL PROTECTED] wrote:
Hi Tim,
Tim OBrien wrote:
Good summary, comments inline...
--- Jörg Schaible [EMAIL PROTECTED] wrote:
4/ Copied c-codec classes in official API
To remove a dependency to c-codec the digest and hex utilities have been
copied to
Tim OBrien wrote:
--- Jörg Schaible [EMAIL PROTECTED] wrote:
4/ Copied c-codec classes in official API
To remove a dependency to c-codec the digest and hex utilities have been
copied to c-id, but they are now publicly available in the o.a.c.id
namespace.
Martin already proposed to move them
On 1/14/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi folks,
reviewing c-id I found more issues to resolve before releasing 1.0 final.
Since I already reported different complaints, I create here a summary of
anything already reported and all new issues.
1/ Concept of
As per the general thrust of Phil's mail, we should remove everything
thats complex and not working and get a simple 1.0 out there. We can
then grow from that point as and when the desire arises.
Stephen
Phil Steitz wrote:
On 1/14/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi folks,
Hi Phil,
comments in line again ...
Phil Steitz wrote:
On 1/14/06, Jörg Schaible [EMAIL PROTECTED] wrote:
Hi folks,
reviewing c-id I found more issues to resolve before releasing 1.0 final.
Since I already reported different complaints, I create here a summary of
anything already reported
Hi Stephen,
Stephen Colebourne wrote:
As per the general thrust of Phil's mail, we should remove everything
thats complex and not working and get a simple 1.0 out there. We can
then grow from that point as and when the desire arises.
As answered to Phil, UUID is now part of c-id for two
Hi Stephen,
Stephen Colebourne wrote:
Tim OBrien wrote:
--- Jörg Schaible [EMAIL PROTECTED] wrote:
4/ Copied c-codec classes in official API
To remove a dependency to c-codec the digest and hex utilities have been
copied to c-id, but they are now publicly available in the o.a.c.id
namespace.
Hi fellows,
two of the issues have already be solved (see inline comments), but I have
two new ones, see at the bottom.
Jörg Schaible wrote:
[snip]
3/ xxxStateImpl classes
The javadoc of ReadOnlyResourceStateImpl implies that the implementation
tries to discover (well, use c-discovery) to
snip/
For me the question is, does a normal user really care about the specifics
of an unique id. The most difference is the returned type of the id,
because that may impact other parts of the code (e.g. DB).
I think many apps will care about more than just the type as in string
or numeric,
J?rg Schaible wrote:
8/ Prefix generators
We have 3 generators, that add a prefix to the generated id. All 3 classes
to mainly the same for 3 different StringIdentifierGenerators.
Proposal: Since we have a lot more StringIdentifierGenrators (e.g. the
UUIDIdentifierGenerators a
On 1/14/06, Michael Heuer [EMAIL PROTECTED] wrote:
Jörg Schaible wrote:
8/ Prefix generators
We have 3 generators, that add a prefix to the generated id. All 3 classes
to mainly the same for 3 different StringIdentifierGenerators.
Proposal: Since we have a lot more
28 matches
Mail list logo
