directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Vermillard (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-34) New transport type: Java Communications API
Date Thu, 05 Jan 2006 11:44:01 GMT
    [ http://issues.apache.org/jira/browse/DIRMINA-34?page=comments#action_12361835 ] 

Julien Vermillard commented on DIRMINA-34:
------------------------------------------

There is some issues with Sun's JCA 3.0. It broken compatibility with external implementation,
using weirdo hacks in the common code.

Extract of http://www.rxtx.org 

# Sun Dec 18 2005 After Sun Javax.comm broke their flexible 2.0 API, removed it and replaced
it with an API version 3.0 rxtx can not support for almost all platforms rxtx supports, the
rxtx 2.0 release has been hidden and rxtx 2.1 which replaces the API in package gnu.io is
being offered to avoid confusion. The rxtx 2.0 support will resume if the design issues are
resolved by Sun.

http://mailman.qbang.org/pipermail/rxtx/20051216/001960.html

So I wait and see for see if an implementation on Sun's Java Communication API V3 is possibe
or I need to switch on the LGPLed rxtx.org API

> New transport type: Java Communications API
> -------------------------------------------
>
>          Key: DIRMINA-34
>          URL: http://issues.apache.org/jira/browse/DIRMINA-34
>      Project: Directory MINA
>         Type: New Feature
>     Versions: 0.7
>     Reporter: Trustin Lee
>      Fix For: 0.9.1

>
> Java Communications API provides ways to access serial and parallel ports available.
 We could implement transport type implementation of Java Communications to provides users
access to serial and parallel ports.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message