[
https://issues.apache.org/jira/browse/DERBY-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452094#comment-13452094
]
Dag H. Wanvik commented on DERBY-5920:
--------------------------------------
I think for this to be opened up again, other drivers need to implement the
extensions made in the protocol in recent Derby releases. Other driver vendors
would need to cooperate with the community to ensure they build in the required
extension for opening to be safe.
> Network Server should accept DRDA connections from drivers with the StarQuest
> PRDID "SIG"
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-5920
> URL: https://issues.apache.org/jira/browse/DERBY-5920
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Affects Versions: 10.9.1.0
> Environment: Any
> Reporter: David Brown
> Labels: DRDA, SIG, StarQuest, StarSQL, client, network
>
> Background - Refer to DERBY-5565
> "Derby Network Server has been changed to reject client connections from
> clients that are not Derby Network Client (Those that do not send PRDID
> starting with DNC).
> Rationale for Change: There are currently no known supported network clients
> for Derby Network Server other than Derby Network Client."
> This is incorrect - StarQuest Ventures has a shipping DRDA-compliant network
> client "StarSQL for Java" that has supported Derby since August 2008. It is
> listed at http://wiki.apache.org/db-derby/UsesOfDerby.
> This change means that we can now only use an older version of Derby until
> our PRDID is added.
> Our PRDID is SIG - see
> http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Fddp%2Frbal1exitpgms.htm
> for a list of DRDA PRDID's.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
