You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <Ri...@Sun.COM> on 2005/08/17 00:51:20 UTC
drda product identifier
DRDA publishes a list of supporting vendors (see
http://www.opengroup.org/dbiop/prodid.htm). Each of these vendors has
its own product id. Derby isn't in this list although Cloudscape half
is. Right now:
o The Derby network client makes up its own product identifier: DNC.
o The Derby network server uses the Cloudscape product identifier: CSS.
This seems a little odd to me:
o Should Derby use the id of a product sold by IBM? This could give rise
to lots of mischief.
o Other vendors who supply both clients and servers use the same product
identifer for both. Why don't we follow this common practice?
Derby could apply for its own product identifier to be used by both
client and server. I'm happy to push this application forward if the
list thinks that's the right thing to do.
Feedback, other thoughts?
Thanks,
-Rick
Re: drda product identifier
Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
>>>>>>>>>>>> Rick Hillegas wrote (2005-08-16 15:51:20):
> Derby could apply for its own product identifier to be used by both
> client and server. I'm happy to push this application forward if the
> list thinks that's the right thing to do.
>
> Feedback, other thoughts?
I definitely believe this is the right thing to do.
Bernt
--
Bernt Marius Johnsen, Database Technology Group,
Sun Microsystems, Trondheim, Norway
Re: drda product identifier
Posted by Kathey Marsden <km...@sbcglobal.net>.
Rick Hillegas wrote:
> Hi Kathey,
>
> Thanks for these good points. I agree that Derby 10.2 needs to
> continue to interoperate with these clients and that we need to build
> out our compatibility tests. At some point, I'd like to circulate a
> proposal for what changes we plan to make to the 10.2 client and
> server. That proposal should address how we interoperate with old
> clients and how we plan to test compatibility.
>
Thank you so much for your due diligence in this area!
Kathey
Re: drda product identifier
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Kathey,
Thanks for these good points. I agree that Derby 10.2 needs to continue
to interoperate with these clients and that we need to build out our
compatibility tests. At some point, I'd like to circulate a proposal for
what changes we plan to make to the 10.2 client and server. That
proposal should address how we interoperate with old clients and how we
plan to test compatibility.
Thanks,
-Rick
Kathey Marsden wrote:
>Rick Hillegas wrote:
>
>
>
>>I have begun the process of applying for a Derby product id: DRB. Will
>>keep the list posted.
>>
>>
>
>With the new id I think it is important that Derby Client 10.1 and
>other clients which currently work with Derby continue to work.
>If you make this change could you just leave the server sending CSS to
>the Derby 10.1 client, JCC and ODBC?
>When new versions of JCC and ODBC recognize the new product id,
>someone from IBM can change network server to start sending DRB to
>these clients.
>
>In general I think we have to be careful about upgrade scenarios because
>right now we have no upgrade tests in derbyAll and we have no
>backward/forward client compatibility testing. I'll add Jira entries
>for these test items. Please tread lightly. I think it is really
>important that users already using Derby see a seamless upgrade and
>that client maintain backward/forward compatibility with server.
>
>Thanks
>
>Kathey
>
>
>
>
>
>
Re: drda product identifier
Posted by Kathey Marsden <km...@sbcglobal.net>.
Rick Hillegas wrote:
> I have begun the process of applying for a Derby product id: DRB. Will
> keep the list posted.
With the new id I think it is important that Derby Client 10.1 and
other clients which currently work with Derby continue to work.
If you make this change could you just leave the server sending CSS to
the Derby 10.1 client, JCC and ODBC?
When new versions of JCC and ODBC recognize the new product id,
someone from IBM can change network server to start sending DRB to
these clients.
In general I think we have to be careful about upgrade scenarios because
right now we have no upgrade tests in derbyAll and we have no
backward/forward client compatibility testing. I'll add Jira entries
for these test items. Please tread lightly. I think it is really
important that users already using Derby see a seamless upgrade and
that client maintain backward/forward compatibility with server.
Thanks
Kathey
Re: drda product identifier
Posted by Rick Hillegas <Ri...@Sun.COM>.
I have begun the process of applying for a Derby product id: DRB. Will
keep the list posted.
Cheers,
-Rick
Rick Hillegas wrote:
> DRDA publishes a list of supporting vendors (see
> http://www.opengroup.org/dbiop/prodid.htm). Each of these vendors has
> its own product id. Derby isn't in this list although Cloudscape half
> is. Right now:
>
> o The Derby network client makes up its own product identifier: DNC.
>
> o The Derby network server uses the Cloudscape product identifier: CSS.
>
> This seems a little odd to me:
>
> o Should Derby use the id of a product sold by IBM? This could give
> rise to lots of mischief.
>
> o Other vendors who supply both clients and servers use the same
> product identifer for both. Why don't we follow this common practice?
>
> Derby could apply for its own product identifier to be used by both
> client and server. I'm happy to push this application forward if the
> list thinks that's the right thing to do.
>
> Feedback, other thoughts?
>
> Thanks,
> -Rick