[omniORB] Standard ?

[Boris Khanales]

Well well well. The next question will be ....


In orbix you can setup timeout for non-oneway calls.
If you want Enviroment to cury out exceptions only
than it isn't very logical to have it in every remote
call, but is it realy correct interpritation for Enviroment?
I'm very far away from thinking that IONA presents the
standard, but why whould you call exception - "Enviroment" ?

Oops, the mailbox realy going to overflow now.



> From owner-omniorb-list@orl.co.uk Thu Apr  9 15:46 EDT 1998
> Date: Thu, 9 Apr 1998 13:37:40 -0400
> From: Ian Brennan <ibrennan@iona.com>
> Mime-Version: 1.0
> To: "dcmay@object-workshops.com" <dcmay@object-workshops.com>
> Cc: "'Mark Little'" <M.C.Little@ncl.ac.uk>,
        "omniorb-list@orl.co.uk" <omniorb-list@orl.co.uk>
> Subject: Re: [omniORB] Standard ?
> Content-Transfer-Encoding: 7bit
> 
> > Unable to find any reference in the CORBA spec which would
> > REQUIRE an ORB implementation to support an Environment parameter. (I've
> > got to admit that I haven't looked TOO hard, though). The wording for
> > 16.17 seems to indicate that it is not needed if a compiler supports
> > native C++ exceptions:
> 
> It's not required, in fact I believe it's _illegal_ to support the Environment
> parameter in mappings for compilers that _do_ support exceptions. Open to
> correction on this, tho.
> 
> [...]
> 
> > > For true language independence this will need to be done anyway, since
> > > clients written in C, for example, will be sending Environments all the
> > > time.
> > 
> > It is my understanding that at the client/server boundary, the ORBs
> > should handle any necessary conversion between language-specific
> > implementation issues, such as exceptions. As such, a server written in
> > C++, and using native C++ exceptions, should be able to throw an
> > exception, have it caught by the server ORB, converted into whatever
> > exception class it maps to, and passed back to the client via IIOP. For a
> > client written in C, it would be converted into its C mapping, and passed
> > up the calling chain via the Environment parameter until it was handled.
> [...]
> 
> Agreed.  That's the whole point of using CORBA, innit?
> 
> And first prize goes to the one who can tell me how exceptions are mapped in
> COBOL...
> 
> Ian.
> ----
>