Issue 2062:  stream controllers and endpoints in browser-type scenario needed (avstreams-rtf)
Source:  (, )
Nature:  Enhancement
Severity:  Minor
Summary: Summary: This is related to the need to put stream controllers and
 endpoints in a browser-type sceanario. In this scenario the
 StreamEndPoint_A in the browser calls request_connection() on
 StreamEndPoint_B on the server. Because the StreamEndPoint_B
 is behind the firewall it must provide for all of the listen
 addresses of flows and must also provide the information about
 their direction and format. The StreamEndPoint_A in the browser
 can then decide which of the flows it can connect to based on name
 or directionality and format.
 
 

Resolution: 
Revised Text: 
Actions taken:
October 7, 1998: received issue
Discussion: 

End of Annotations:=====
Return-Path: <www>
Date: Wed, 7 Oct 1998 09:47:58 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Damian McGrath
Company: IONA Technologies
Email: dmcgrath@iona.com
Notification: No
Specification: Control and  Management of Audio/Video Streams
Section: 2
Formal #: 98-07-12
Version: 1.0
Revision_Date: 
Page: 
Nature: Enhancement
Severity: Minor
full_desc: This is related to the need to put stream controllers and
endpoints in a browser-type sceanario. In this scenario the
StreamEndPoint_A in the browser calls request_connection() on
StreamEndPoint_B on the server. Because the StreamEndPoint_B
is behind the firewall it must provide for all of the listen
addresses of flows and must also provide the information about
their direction and format. The StreamEndPoint_A in the browser
can then decide which of the flows it can connect to based on name
or directionality and format.



submit: Submit Issue Report