harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1375) [classlib][net]Refine native code interface of setSocketOption
Date Wed, 06 Sep 2006 10:17:23 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1375?page=comments#action_12432803 ] 
Alexey Varlamov commented on HARMONY-1375:

Just for the record, copy-pasting suggestions expressed on the dev-list.

1) Why at all we clone underlying OS interface to Java with extra
mapping JAVASOCKOPT_* to HY_SO_*? Let's have a clean API with
specialized methods as XXXSocket classes have: setTTL(int) ,
isReuseAddress() etc.

2) At least we could provide more typified [s|g]etOption() methods,
which  take/return primitive values instead of wrappers. At first
glance int and boolean would fit all needs, am I wrong? This way, type
mismatch will be found immediately during compilation. Though this
would not detect optid and value type disparity (until runtime)...

> [classlib][net]Refine native code interface of setSocketOption
> --------------------------------------------------------------
>                 Key: HARMONY-1375
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1375
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Jimmy, Jing Lv
>            Priority: Minor
> According to discussion on Harmony 1295, a refine may be made on native method setSocketOption
of java.net. More discussion on this (if necessary/howto) is welcome.

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


View raw message