Issue 383: Callbacks in IIOP (interop) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: Callbacks in IIOP are to be implemented by getting the server to connect back to client and act as a client itself. If this could be changed it would really help from firewall perspective. Resolution: closed with no revision required Revised Text: Actions taken: December 2, 1996: received issue March 26, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Date: Wed, 10 Dec 1997 16:49:32 -0500 From: ter@holta.ho.lucent.com (T E Rutt) To: interop@omg.org Subject: Interop 1.2 RTF Conference call (Proposed revisions and issues) To: Interop 1.2 RTF Subject: Dec 19, Conference Call From: Tom Rutt, RTF Chair I have attached my proposed Resolutions of Issues for ORB Interoperability 1.2 Revision Task Force. There was no meeting of the RTF at the NJ meeting, since everyone is so busy I decided to take a whack at coming up with resolutions for the issues. We need further discussion on some of these issues, as indicated in the actions section of each issue. A conference Call is scheduled for Friday, December 19, at 11:00 EST. I have the bridge reserved for 2 hours. The bridge phone number (16 ports reserved) is: +1 630 224 444 Conference Code 674 369 Let me know if you will participate, so I can ensure 16 is enough ports. Tom Rutt Issue 383: Callbacks in IIOP (interop) Click here for this issue's archive. Source: IONA (Mr. Justin Mason, jmason@iona.com) Nature: Uncategorized Severity: Summary: Callbacks in IIOP are to be implemented by getting the server to connect back to client and act as a client itself. If this could be changed it would really help from firewall perspective. Resolution: Proposed To change current restricted binding behaviour by allowing responder of GIOP binding to invoke operations, either by revision or by waiting for firewall RFP submission. Revised Text: Actions taken: To Vote, is this a bug or a feature expansion? December 2, 1996: received issue