webrtc

generic-library/webrtc

Fork 0

Commit Graph

Author	SHA1	Message	Date
tommi@webrtc.org	102b2270c7	First version of the peerconnection client application for Linux. I made several updates to the Windows version as well so that both implementations share a big portion of the code. The underlying PeerConnection notifications have changed a bit since the last update so that there's still a known issue that I plan to fix in my next change: // TODO(tommi): There's a problem now with terminating connections: // When ending a conversation, both peers now send a signaling message // that indicates that their ports are closed (port=0). The trouble this // causes us here is that we can interpret such a message as an invite // to a new conversation. So, currently there is a bug that ending // a conversation can immediately start a new one. // To fix this I plan to change how conversations start and have a special // notification message via the server that prepares a client for a // conversation instead of automatically recognizing the first signaling // message as an invite. Review URL: http://webrtc-codereview.appspot.com/112008 git-svn-id: http://webrtc.googlecode.com/svn/trunk@446 4adac7df-926f-26a2-2b94-8c16560cd09d	2011-08-25 15:03:52 +00:00
tommi@google.com	b0d7a87bb0	Mock implementation for the UI of the linux version of the peerconnection client. At this point, there's not a lot too it as it only shows what the UI will look like and basically mimics what the Windows version does presently. Review URL: http://webrtc-codereview.appspot.com/92018 git-svn-id: http://webrtc.googlecode.com/svn/trunk@344 4adac7df-926f-26a2-2b94-8c16560cd09d	2011-08-10 09:03:29 +00:00

Author

SHA1

Message

Date

tommi@webrtc.org

102b2270c7

First version of the peerconnection client application for Linux.

I made several updates to the Windows version as well so that both
implementations share
a big portion of the code.
The underlying PeerConnection notifications have changed a bit since the last
update
so that there's still a known issue that I plan to fix in my next change:

  // TODO(tommi): There's a problem now with terminating connections:
  // When ending a conversation, both peers now send a signaling message
  // that indicates that their ports are closed (port=0).  The trouble this
  // causes us here is that we can interpret such a message as an invite
  // to a new conversation.  So, currently there is a bug that ending
  // a conversation can immediately start a new one.
  // To fix this I plan to change how conversations start and have a special
  // notification message via the server that prepares a client for a
  // conversation instead of automatically recognizing the first signaling
  // message as an invite.
Review URL: http://webrtc-codereview.appspot.com/112008

git-svn-id: http://webrtc.googlecode.com/svn/trunk@446 4adac7df-926f-26a2-2b94-8c16560cd09d

2011-08-25 15:03:52 +00:00

tommi@google.com

b0d7a87bb0

Mock implementation for the UI of the linux version of the peerconnection client.

At this point, there's not a lot too it as it only shows what the UI will look like and basically mimics what the Windows version does presently.
Review URL: http://webrtc-codereview.appspot.com/92018

git-svn-id: http://webrtc.googlecode.com/svn/trunk@344 4adac7df-926f-26a2-2b94-8c16560cd09d

2011-08-10 09:03:29 +00:00

2 Commits