Release Notes
Introduction
The SSC, or Simultaneous Synchronous Communicator, is a BeOS program enabling two to four individuals, using different computers connected via a network, to exchange messages. The connections between all the individuals are synchronous, meaning they all happen at the same time. All of these synchronous connections must be serviced by the program simultaneously, at the same time. Hence the name, Simultaneous Synchronous Communicator, expresses the ability of the program to address the multiple dimensions of 'at the same time'.
The connections between all the individuals form a conference.
Known Problems
- When the size of a Conference window is changed, the Text view contained in the Scroll views is not changed. This is noticed when a Conference window is enlarged, the text wraps to early and does not fully use the space in the view.
- Workaround:
- Enlarge the Conference window before starting the conference.
Further testing needed
- Testing four computer conference
- Two cases are needed:
- Create a three-computer conference. Add a fourth computer.
- Create two two-computer conferences. Connect them.
- Testing five computer conference
- This should display a warning message and not allow it.
- Barrage of connections received from SSC's
- Windows should be displayed for all connections received.
- Another program connecting on port 5440.
- SSC accepts connections on port 5440.
- With SSC running, tried to connect NetPenguin on port 5440. SSC gave no errors and no indication of invalid connection. NetPenguin gave a standard invalid connection message.
- Needs more testing.
- Operation inside and outside a firewall.
- SSC should not be able to cross the firewall.
- Participants in a conference must be either all inside or all outside the firewall.
Boring Details
The concept is simple:
- Record something (text, etc.)
- Stuff the something into a BMessage.
- Flatten the BMessage
- Stuff flattened BMessage into an RTP packet per RFC1890.
- Transmit it to others in the conference.
- Receive the RTP packet.
- Inflate the BMessage.
- Play or display the something (text, etc.)
- What can you send to the participants in the conference?
- Anything you can add to a BMessage.
What's Done
- Making and Accepting connections
- Entering and Leaving a Conference
- Flattening, transmitting, receiving and inflating BMessages
- Recording and playing Text
What's left
Development
- Recording and playing Audio
- Recording and playing Video
- Expanding the number of participants from four to twelve
- Context Sensitive help
Productization
- Feedback from Human Factors
- Feedback from Users
- Documentation
- Cosmetics
Your Experiences with the SSC
I want to hear about your experience with the SSC. Send an e-mail message describing the experience to
rdscomps@interaccess.com