h6. [[URL_Fetcher]] h6(. » [[URL_Fetcher Protocol module interface|Protocol module interface]] h6((. » Protocol_GetData h2. Protocol_GetData h5. (SWI SWI_base+0) Start retrieving data. |_<^{width:4em}. Entry ||| |<^. R0 |\2<^. Flags | ||<^. Bits 0-30 |<^(. As specified by client in [[URL_GetURL]] | ||<^. Bit 31 |<^(. R7 is valid | |<^. R1 |\2<^. Session identifier | |<^. R2 |\2<^. Method | |<^. R3 |\2<^. URL (including fetch scheme) | |<^. R4 |\2<^. Pointer to block of data in addition to URL | |<^. R5 |\2<^. Protocol dependent | |<^. R6 |\2<^. Protocol dependent | |<^. R7 |\2<^. If R0:31 is set, proxy URL information | |_<^{width:4em}. Exit | | |<^. R2 |\2<^. Protocol status word (see [[URL_Status]] for details) | |\3<^. All other registers are protocol-dependent. | h4. Interrupts Interrupt status is protocol module dependent. h4. Re-entrancy SWI re-entrancy is protocol module dependent. h4. Use This call is used to start retrieving data. The protocol module should raise any events for the client via the session identifier provided in R1. The URL module calls this SWI in response to one of its clients calling SWI [[URL_GetURL]]. The proxy URL information specified in R7 (if R0:31 is set) gives the location of the proxy to be used in the format of a URL. For example, "http://www-cache.demon.co.uk:8080/". This information is supplied by the URL module and not the client. The protocol module must note that on a proxied request, the target URL indicated by R3 may not have the same fetch scheme. For example, it might be an ftp: URL being proxied through an HTTP proxy service. Note that the session identifiers passed in R1 are _not_ the same identifiers used by clients to talk to the URL module. They are _not_ interchangeable. h4. See also * [[URL_GetURL]] * [[URL_ProtocolRegister]] * [[URL_ProtocolDeregister]] * [[Protocol_Stop]] * [[HTTP_GetData]] h4. Related vectors None