The response includes an HTTP status code, a set of response headers, and an XML response body. For more information, see About Storage Analytics Logging and Azure Logging: Using Logs to Track Storage Requests. Using this header is highly recommended for correlating client-side activities with requests received by the server. Provides a client-generated, opaque value with a 1 KiB character limit that is recorded in the analytics logs when storage analytics logging is enabled. For more information, see Versioning for the Azure Storage Services. Specifies the version of the operation to use for this request. For more information, see Authorize requests to Azure Storage. Specifies the Coordinated Universal Time (UTC) for the request. Specifies the authorization scheme, account name, and signature. The following table describes required and optional request headers. For more information, see Setting Timeouts for Queue Service Operations. The timeout parameter is expressed in seconds. By default, a single message is peeked from the queue with this operation. A nonzero integer value that specifies the number of messages to peek from the queue, up to a maximum of 32. The following parameters may be specified on the request URI. When making a request against the emulated storage service, specify the emulator hostname and Queue service port as 127.0.0.1:10001, followed by the emulated storage account name: Method Replace myaccount with the name of your storage account, and myqueue with the name of your queue: Method The Peek Messages request may be constructed as follows. The Peek Messages operation retrieves one or more messages from the front of the queue, but does not alter the visibility of the message. wpz Peek Classic Packet File (classic compressed) apc/.pkt Peek Classic Packet File (classic format) apc/.pkt Peek Packet File (tagged format) The formatIndex is the index into the format combo box in Peek's Save dialog: Void Save(BSTR FilePath, INT formatIndex) Set to True to start capture, set to False to stop capture
You acquire a reference to a document object through (BSTR File). The Document class represents a capture or file window. If the file is a capture template file, returns an IDispatch* reference to the Document object for that capture window. If the given file is a packet trace file, returns an IDispatch* reference to the Document object that file window. All other properties and methods are unimplemented. The Documents object exists only to open files. Rearranges deck chairs on your MDI Titanic Title of main window (usually the application name)
The object that knows how to open documents
MyDoc.Save("C:\foo\My Saved Packet List.txt", 4) COM Application Object Reference Read-Only Properties MyDoc = ("C:\foo\My Capture Template.ctf") ' create a new capture window, using an existing capture template MyApp = CreateObject("EtherPeek.Application") MyApp = GetObject(, "EtherPeek.Application") Here's some Visual Basic sample code: ' acquire connection to app
Text packet lists are especially good for extracting summary strings and addresses. To extract information out of a capture, save the capture to a file and then parse the file. To specify a set of filters, use the Peek GUI to define them and save them as part of your capture template file. Save the above capture window or packet list file to a file, you choose the file path and the format.Start/stop capture in the above capture window.Create a new capture window by opening a capture template file.Peek's COM interface now supports a few useful operations: For AiroPeek/AiroPeek NX v2.0 or higher, EtherPeek v5.1 or higher, EtherPeek NX v2.1 or higher, GigaPeek NX v1.0 or higher, Omnipeek v1.0 or higher, WANPeek NX v1.0 or higher
0 kommentar(er)
