IHTMLOpsProfile::doReadRequestIHTMLOpsProfile::doReadRequest*
*Contents  *Index  *Topic Contents
*Previous Topic: IHTMLOpsProfile::addReadRequest
*Next Topic: IHTMLOptionButtonElement

IHTMLOpsProfile::doReadRequest


HRESULT doReadRequest( 
    VARIANT usage,
    VARIANT fname,
    VARIANT domain,
    VARIANT path,
    VARIANT expire,
    VARIANT reserved 
);

Performs the compound request accumulated in the read request queue.

usage
Type of access requested. This usage code should be one of the 13 codes defined by the Internet Privacy Working Group (IPWG), as described in the following table.
Usage code Meaning
0 Used for system administration.
1 Used for research and/or product development.
2 Used for completion and support of current transaction.
3 Used to customize the content and design of a site.
4 Used to improve the content of a site including advertisements.
5 Used for notifying visitors about updates to the site.
6 Used for contacting visitors for marketing of services or products.
7 Used for linking other collected information.
8 Used by a site for other purposes.
9 Disclosed to others for customization or improvement of the content and design of the site.
10 Disclosed to others, who may contact you, for marketing of services and/or products.
11 Disclosed to others, who may contact you, for marketing of services and/or products, but you will have the opportunity to ask a site not to do this.
12 Disclosed to others for any other purpose.
fname
Optional. "Friendly name" of the party requesting access to private information. For security reasons, it is not enough for the user agent to display this friendly name to the end user. In addition to this friendly name, it is essential to display the URL that originates the script requesting profile access. If this script originates from a secure connection (for example, SSL), the SSL certificate can also be used to reliably identify the party requesting access.
domain
Optional. Which pages the user's choice will apply to in the future, besides the current one; the specification follows the cookie standard (RFC-2109 http://www.cis.ohio-state.edu/htbin/rfc/rfc2109.html).
path
Optional. Which pages the user's choice will apply to in the future, besides the current one; the specification follows the cookie standard (RFC-2109 http://www.cis.ohio-state.edu/htbin/rfc/rfc2109.html).
expire
Reserved; do not use.
reserved
Reserved; do not use.

See also addReadRequest

Up Top of Page
© 1997 Microsoft Corporation. All rights reserved. Terms of Use.