Re: RPC and Call Identifier????
From: Greg Kapoustin [MSFT] (grigorik_at_online.microsoft.com)
Date: 08/26/04
- Next message: John E: "Inhibiting a default route"
- Previous message: BobK: "connect() call blocks forever"
- In reply to: moon: "Re: RPC and Call Identifier????"
- Next in thread: moon: "Re: RPC and Call Identifier????"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 11:55:53 -0700
The call identifier represents the count of the call being made. The count
is incremented during each new call from a given client process to a given
server process over a given protocol. This is used to keep track of the
individual calls.
For more detailed information on this and other wire protocol parameters,
you can consulet:
http://www.opengroup.org/onlinepubs/9629399/chap12.htm
>From the document:
The call_id Field
Each run-time protocol message contains a call_id field. This field is used
by the caller to guarantee that it is matching the proper response and
request. Otherwise, responses for the wrong call, or orphaned responses from
calls that were cancelled, and the cancel timed out, could be confused with
current responses. The caller must guarantee that at any time, all call_ids
for all outstanding messages for the same association group are distinct.
The server just returns the call_id on the corresponding message.
The call_id field is also used to guarantee proper matching of bind_ack,
bind_nak or alter_context_response messages in order to guarantee proper
behaviour under certain conditions; for example, cancel timeout causes an
orphan.
Note:
The most straightforward implementation is for each client process to
maintain a single u_int32 sequence number counter to use for the call_id.
Alternatively, the client may assign a value representing a call data
structure, and use that, provided it does sufficient bookkeeping to insure
that it cannot be reused if a call is cancelled and times out, at least
until the the entire orphaned response is received.
Greg
-- This posting is provided "AS IS" with no warranties, and confers no rights. "moon" <only_forme4@hotmail.com> wrote in message news:2afc1efd.0408101233.7c3696cc@posting.google.com... > "Greg Kapoustin [MSFT]" <grigorik@online.microsoft.com> wrote in message > news:<4117e376$1@news.microsoft.com>... >> Can you please be more specific about your question? Are you asking >> about >> interpreting the RPC call_id found in the network sniff, or something >> else? >> >> Greg >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "moon" <only_forme4@hotmail.com> wrote in message >> news:2afc1efd.0408070017.6c101884@posting.google.com... >> > Hi , >> > >> > I really like to know how to set the "Call Identifier" for a MSRPC >> > call? I would also be greatful if you can explain little about this >> > attribute??? >> > >> > Thank you for your help in advance! >> > >> > Yours, > > Yes exactly!! The one that i can see while sniffing!!! As i searched > on the new I found alot of .h files that include it in the header > section of RPC call!! But i don't know how to set it in MSRPC??? And > also what its exact functionallity??
- Next message: John E: "Inhibiting a default route"
- Previous message: BobK: "connect() call blocks forever"
- In reply to: moon: "Re: RPC and Call Identifier????"
- Next in thread: moon: "Re: RPC and Call Identifier????"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
