tag:blogger.com,1999:blog-13033340.post2567337008630862987..comments2023-04-12T07:48:42.117-04:00Comments on Kundan Singh: Voice and Video Communications on WebKundan Singhhttp://www.blogger.com/profile/10408946176930869078noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13033340.post-26687555167991693862012-01-19T01:27:30.220-05:002012-01-19T01:27:30.220-05:00Good post. I was surfing the net and come across y...Good post. I was surfing the net and come across your site. There are lot of <a href="http://www.peoplelink.in" rel="nofollow">video conferencing software</a> in the market now. Somebody suggest which one would be the better for small business for better business communications.Anonymoushttps://www.blogger.com/profile/15207328228655221131noreply@blogger.comtag:blogger.com,1999:blog-13033340.post-27203272376989916392011-08-21T20:41:16.326-04:002011-08-21T20:41:16.326-04:00A couple of comments w.r.t your post. Would apprec...A couple of comments w.r.t your post. Would appreciate if you can provide some clarification around these.<br /><br />1. Using REST API's in conjunction with WebSockets seems counter-intuitive to me w.r.t setting up communication sessions. The way I understand WebSockets, you use the initial HTTP handshake to upgrade your connection to WS. Once established, you exchange data in any format of your choice between the client and the server. In this set up, I can simply envision the data exchanged between the client and server to communicate the intent of the request in the payload (like JSON or XML) The use of subsequent HTTP GET or POST requests in some ways defeats the purpose of WebSockets.<br /><br />2. Your example of creating a "conference" for a simple two party call seems counter-intuitive as well. I can understand if the intent of the request was to set up a conference/multi party call. Would you mind elaborating this choice vs. simply having the server route the request to Bob?Venkateshhttps://www.blogger.com/profile/15893132887136527161noreply@blogger.com