serenity/Services/ProtocolServer/ProtocolServer.ipc

endpoint ProtocolServer = 9
{
    // Basic protocol
    Greet() => (i32 client_id)

    // FIXME: It would be nice if the kernel provided a way to avoid this
    DisownSharedBuffer(i32 shbuf_id) => ()

    // Test if a specific protocol is supported, e.g "http"
    IsSupportedProtocol(String protocol) => (bool supported)

    // Download API
    StartDownload(String url, IPC::Dictionary request_headers) => (i32 download_id)
    StopDownload(i32 download_id) => (bool success)
}
ProtocolServer+LibProtocol: Introduce a server for handling downloads This patch adds ProtocolServer, a server that handles network requests on behalf of its clients. The first protocol implemented is HTTP. The idea here is to use a plug-in architecture where any number of protocols can be added and implemented without having to mess around with each client program that wants to use the protocol. A simple client API is provided through LibProtocol::Client. :^) 2019-11-23 21:45:33 +01:00			`endpoint ProtocolServer = 9`
			`{`
			`// Basic protocol`
LibIPC: Get client/server PIDs using getsockopt(SO_PEERCRED) Instead of passing the PIDs back and forth in a handshake "Greet" message, just use getsockopt(SO_PEERCRED) on both sides to get the same information from the kernel. This is a nice little simplification of the IPC protocol, although it does not get rid of the handshake since we still have to pass the "client ID" from the server to each client so they know how to refer to themselves. This might not be necessary and we might be able to get rid of this later on. 2019-12-06 18:39:59 +01:00			`Greet() => (i32 client_id)`
ProtocolServer+LibProtocol: Introduce a server for handling downloads This patch adds ProtocolServer, a server that handles network requests on behalf of its clients. The first protocol implemented is HTTP. The idea here is to use a plug-in architecture where any number of protocols can be added and implemented without having to mess around with each client program that wants to use the protocol. A simple client API is provided through LibProtocol::Client. :^) 2019-11-23 21:45:33 +01:00
ProtocolServer: Send the download payload to clients as a shared buffer The DownloadFinished message from the server now includes a buffer ID that can be mapped into the client program. To avoid prematurely destroying the buffer, the server will hang on to it until the client lets it know that they're all good. That's what the ProtocolServer::DisownSharedBuffer message is about. In the future it would be nice if the kernel had a mechanism to allow passing ownership of a shared buffer along with an IPC message somehow. 2019-11-23 22:11:44 +01:00			`// FIXME: It would be nice if the kernel provided a way to avoid this`
Kernel+LibC: Rename shared buffer syscalls to use a prefix This feels a lot more consistent and Unixy: create_shared_buffer() => shbuf_create() share_buffer_with() => shbuf_allow_pid() share_buffer_globally() => shbuf_allow_all() get_shared_buffer() => shbuf_get() release_shared_buffer() => shbuf_release() seal_shared_buffer() => shbuf_seal() get_shared_buffer_size() => shbuf_get_size() Also, "shared_buffer_id" is shortened to "shbuf_id" all around. 2020-02-28 11:45:19 +01:00			`DisownSharedBuffer(i32 shbuf_id) => ()`
ProtocolServer: Send the download payload to clients as a shared buffer The DownloadFinished message from the server now includes a buffer ID that can be mapped into the client program. To avoid prematurely destroying the buffer, the server will hang on to it until the client lets it know that they're all good. That's what the ProtocolServer::DisownSharedBuffer message is about. In the future it would be nice if the kernel had a mechanism to allow passing ownership of a shared buffer along with an IPC message somehow. 2019-11-23 22:11:44 +01:00
ProtocolServer+LibProtocol: Introduce a server for handling downloads This patch adds ProtocolServer, a server that handles network requests on behalf of its clients. The first protocol implemented is HTTP. The idea here is to use a plug-in architecture where any number of protocols can be added and implemented without having to mess around with each client program that wants to use the protocol. A simple client API is provided through LibProtocol::Client. :^) 2019-11-23 21:45:33 +01:00			`// Test if a specific protocol is supported, e.g "http"`
			`IsSupportedProtocol(String protocol) => (bool supported)`

			`// Download API`
ProtocolServer: Support request headers You can now pass a dictionary of request headers when starting a new download in ProtocolServer. The HTTP and HTTPS protocol will include the headers in their requests. 2020-05-21 12:27:42 +02:00			`StartDownload(String url, IPC::Dictionary request_headers) => (i32 download_id)`
ProtocolServer+LibProtocol: Introduce a server for handling downloads This patch adds ProtocolServer, a server that handles network requests on behalf of its clients. The first protocol implemented is HTTP. The idea here is to use a plug-in architecture where any number of protocols can be added and implemented without having to mess around with each client program that wants to use the protocol. A simple client API is provided through LibProtocol::Client. :^) 2019-11-23 21:45:33 +01:00			`StopDownload(i32 download_id) => (bool success)`
			`}`