Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have installed an Icecast server to simulate a radio station. Icecast use HTTP as a protocol but I wonder if, for audio only, it provides a good enough sound quality. I've heard about RTSP and it seems more convenient for audio streaming - but I can't find any Icecast equivalent using RTSP protocols.
Can I have your thoughts on it?
Thanks!
Audio quality depends on the codec and it's bit-rate. Transport is pretty much irrelevant.
The use of HTTP with protocols that support adaptive bitrates. This is theoretically a bad fit... however, HTTP is widely interoperable. It has countless implementations both on the server and client sides, which is great.
RTSP isnt known for its interoperability... Normal RTSP servers close inactive control connections. Well-behaving servers will still keep RTSP sessions for a while longer than HTTP...
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
HTTP/1.1 has served the Web well for more than fifteen years, but its
age is starting to show.
Can anybody explain what is the main difference between HTTP 1.1 and 2.0?
Is there any change in the transport protocol?
HTTP/2 supports queries multiplexing, headers compression, priority and more intelligent packet streaming management. This results in reduced latency and accelerates content download on modern web pages.
More details here.
HTTP 2.0 is a binary protocol that multiplexes numerous streams going over a single (normally TLS-encrypted) TCP connection.
The contents of each stream are HTTP 1.1 requests and responses, just encoded and packed up differently. HTTP2 adds a number of features to manage the streams, but leaves old semantics untouched.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I know my question is broad, but I have no clue where to start my research.
How can one implement VoIP on a server? I am fairly certain it does not use the http/https protocol. If so, what standard/famous protocols one can use? are there any open-source ones? What are good references to start working on that?
Start by looking at the SIP,RTP and RTCP protocols. I believe they form a minimalistic set of required protocols for VoiP
Some relevant open source projects:
http://www.fsf.org/campaigns/priority-projects/priority-projects/highpriorityprojects#Replaceskype
"There are a number of such programs, such as Ekiga, Twinkle, Coccinella, QuteCom, and Jitsi. Unfortunately, these programs only replace some of Skype's functionality, and only in some situations. WebRTC has a mission to enable rich, high quality, Real-Time Communications (RTC) applications to be developed in the browser via simple Javascript APIs and HTML5. Developers should consider helping free software VoIP and video, chat, and multimedia communications projects."
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
EDIT: i would really appreciate a source or an example that talks about this being done.
Some companies have a distributed program written in C++, it runs on different machines, it uses TCP/IP for inter communication between different machines (windows and linux). Is it possible to write a program from the ground up using other languages (python, java) that will be able to join their network?
Yes. Of course, TCP/IP is language agnostic. The key issue is to get the protocol correct.
If you have the specification for what is being communicated (or can reverse-engineer it), then yes. Without knowing what to send, and what to expect back it'll be a losing battle.
Of course! That's why it is a protocol: you don't have to know who is on the other side, as long as it follows the protocol specification
Based on edit:
This info is anywhere, based on the language you want to use. Here is a basic python example for tcp communication
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I want to understand http protocol in depth. Does anyone know where can I find relevant material for HTTP. A few questions that I have in particular are:
Why does when press enter after typing for eg. "google.com" it gets translated to "http://www.google.com" and not "ftp://www.google.com" or something else.
How does the http request gets transferred to a server, what routing algorithm it uses to decide which server to used, and inside that server where to locate the uniform resource".
Any pointers in this direction are most welcome!!
Because HTTP is simply the web standard for requests. We all agreed on using that when the web started, and now we are stuck with it (whether it is good or not).
HTTP stands for 'Hypertext Transfer Protocol' and is in fact the way how to exchange that information you see on your display when browsing.
FTP, and numerous other protocols are their standards (or in general methods) for their purpose. HTTP serves the purpose of communicating between client and server for the web.
And about how HTTP works internally, well, they wrote a few books on it. The standard is described by the IETF: Hypertext Transfer Protocol -- HTTP/1.1.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Correct me if i am wrong with my understanding:
BitTorrent is a protocol used for P2P sharing and it is used by torrent client. BitTorrent protocol have ability to download the files in chunks. Once all the chunks are downloaded the torrent client application will merge them in a single file.
Is there any encryption method is used while transmission of data by BitTorrent protocol or torrent application?
I have seen BitTorrent was earlier open source but after release version 6 it is no more open source. It is about protocol or BitTorrent Client?
Please clear my doubt.
Thanks.
All modern BitTorrent clients support protocol encryption. You can find the specification here.