[omniORB] omniORB 4 feature list

[Jani Niittukari]

When omniORB4 will be released? I've been waiting for a while for the
official wstring/wchar support...

Thanks,

Jani

> -----Original Message-----
> From: owner-omniorb-list@uk.research.att.com
> [mailto:owner-omniorb-list@uk.research.att.com]On Behalf Of Sai-Lai Lo
> Sent: 12. maaliskuuta 2001 18:14
> To: omniorb-list@uk.research.att.com
> Subject: [omniORB] omniORB 4 feature list
>
>
> This list has been requested for some time, sorry for the delay in putting
> it up.
>
>  - GIOP 1.1 and 1.2. (done) Bi-directional GIOP (to be merged).
>
>  - More flexible transports -- SSL, unix domain ... (in progress)
>       When an IOR has multiple transport options available, the
>       transports are ordered into a priority list based on the
>       network address of the destination. For instance, use SSL
>       when the ip address is not one of the intranet.
>
>  - Interceptors, but not the portable interceptor API. (done)
>    - the portable API can be built on top of the omniORB API.
>
>  - wchar, wstring, code set conversion. (done)
>
>  - Fixed point type. (done)
>
>  - Long double type.
>
>  - Current.
>    - and everything which goes with it, e.g. proper _this() semantics.
>
>  - Fault-tolerant client support. (in progress)
>       Understand IOGR. Behave as required by the CORBA Fault
> tolerant spec.
>       An offshoot from this is that the ORB will try all IIOP endpoints
>       in an IOR before giving up.
>
>  - Firewall proxy support. (to be merged)
>       Please read the CORBA Firewall proxy spec. The GIOP proxy is
>       supported. I wonder whether in fact the tcp proxy is more useful in
>       practice. Any comment?
>
>  - AMI (to be merged)
>
>  - Maybe objects by value. (probably will not make it at 4.0)
>
> Any feedback is most welcomed.
>
>
> Sai-Lai