34
edits
Difference between revisions of "Local Webserver"
Jump to navigation
Jump to search
How LocalWebserver works: added see also link
(Created page with "== Overview == The Cloud PR also brings a Wi-Fi Sharing feature. As mentioned in the cloud storage support description, webserver is used for Storag...") |
(How LocalWebserver works: added see also link) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
[[File:AJAX_Files_Manager.png|thumb|200px|AJAX Files Manager]] | |||
The Cloud PR also brings a Wi-Fi Sharing feature. As mentioned in the [[Cloud_Storage_Support|cloud storage support description]], webserver is used for Storage connect, but Wi-Fi Sharing uses it much more. | The Cloud PR also brings a Wi-Fi Sharing feature. As mentioned in the [[Cloud_Storage_Support|cloud storage support description]], webserver is used for Storage connect, but Wi-Fi Sharing uses it much more. | ||
| Line 6: | Line 8: | ||
== Wi-Fi Sharing == | == Wi-Fi Sharing == | ||
[[File:Cloud_tab_Server.png|thumb|200px|Server options in Cloud tab]] | |||
ScummVM now can start a local webserver (using SDL_Net), which provides the Files Manager: users can navigate through directories, download files, create new directories or upload files using the browser on another device. Information about the server is available on the new Options dialog's Cloud tab. Users could launch the webserver there or change the port it's using. | ScummVM now can start a local webserver (using SDL_Net), which provides the Files Manager: users can navigate through directories, download files, create new directories or upload files using the browser on another device. Information about the server is available on the new Options dialog's Cloud tab. Users could launch the webserver there or change the port it's using. | ||
| Line 74: | Line 78: | ||
To parse the request the right way, Client uses a Reader, which could handle reading HTTP GET or POST form/multipart request. It keeps the right state no matter how small the chunks of request are: one can pass the request byte by byte or in buffers of limited size, but Reader won't miss headers end or a boundary. | To parse the request the right way, Client uses a Reader, which could handle reading HTTP GET or POST form/multipart request. It keeps the right state no matter how small the chunks of request are: one can pass the request byte by byte or in buffers of limited size, but Reader won't miss headers end or a boundary. | ||
See also: [[LocalWebserver Data Flow|information]] about LocalWebserver/Client/Reader data flow. | |||