Ntdev,
In the DDK documentation for a TDI client openning a connection
endpoint, it says that the EaBuffer should contain contain an EaName
member of TdiConnectionContext followed by “an EA value that is
usually the address of a client allocated context area in which the =
client
will subsequently maintain state about the endpoint-to-endpoint =
connection
to be established.” What is this area and what structure respresents its
data layout / how should it be allocated?
Thanks,
Jonathan Nicklin
The beginning of user connection context is at EaNameLength + 1 bytes in
EaName buffer.
FILE_FULL_EA_INFORMATION *ea = (FILE_FULL_EA_INFORMATION
*)irp->AssociatedIrp.SystemBuffer;
CONNECTION_CONTEXT conn_ctx = *(CONNECTION_CONTEXT *)(ea->EaName +
ea->EaNameLength + 1);
There’s no structure to represent it.
vlad-ntdev
----- Original Message -----
From: “Jonathan C. Nicklin”
To: “NT Developers Interest List”
Sent: Sunday, February 17, 2002 9:14 PM
Subject: [ntdev] TdiConnectionContext:
Ntdev,
In the DDK documentation for a TDI client openning a connection
endpoint, it says that the EaBuffer should contain contain an EaName
member of TdiConnectionContext followed by “an EA value that is
usually the address of a client allocated context area in which the =
client
will subsequently maintain state about the endpoint-to-endpoint =
connection
to be established.” What is this area and what structure respresents its
data layout / how should it be allocated?
Thanks,
Jonathan Nicklin
Thanks! This has shed a little bit of light on the subject but im
curious if I have to allocate the actually “client context” space.
I thought the CONNECTION_CONTEXT would just be
a pointer to this allocated space… i guess the question is
what structure that represents this “client context.”
-JCN
----- Original Message -----
From: “vlad-ntdev”
To: “NT Developers Interest List”
Sent: Sunday, March 17, 2002 6:22 AM
Subject: [ntdev] Re: TdiConnectionContext:
> The beginning of user connection context is at EaNameLength + 1 bytes in
> EaName buffer.
>
> FILE_FULL_EA_INFORMATION *ea = (FILE_FULL_EA_INFORMATION
> *)irp->AssociatedIrp.SystemBuffer;
>
> CONNECTION_CONTEXT conn_ctx = *(CONNECTION_CONTEXT *)(ea->EaName +
> ea->EaNameLength + 1);
>
> There’s no structure to represent it.
>
> vlad-ntdev
>
> ----- Original Message -----
> From: “Jonathan C. Nicklin”
> To: “NT Developers Interest List”
> Sent: Sunday, February 17, 2002 9:14 PM
> Subject: [ntdev] TdiConnectionContext:
>
>
> Ntdev,
> In the DDK documentation for a TDI client openning a connection
> endpoint, it says that the EaBuffer should contain contain an EaName
> member of TdiConnectionContext followed by “an EA value that is
> usually the address of a client allocated context area in which the =
> client
> will subsequently maintain state about the endpoint-to-endpoint =
> connection
> to be established.” What is this area and what structure respresents its
> data layout / how should it be allocated?
>
> Thanks,
> Jonathan Nicklin
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@verizon.net
> To unsubscribe send a blank email to %%email.unsub%%
It’s a user defined structure that you can use if you want some context to
be passed to you in your event handlers on the endpoint.
-----Original Message-----
From: Jonathan C. Nicklin [mailto:xxxxx@verizon.net]
Sent: Tuesday, February 19, 2002 1:54 AM
To: NT Developers Interest List
Subject: [ntdev] Re: TdiConnectionContext:
Thanks! This has shed a little bit of light on the subject but im
curious if I have to allocate the actually “client context” space.
I thought the CONNECTION_CONTEXT would just be
a pointer to this allocated space… i guess the question is
what structure that represents this “client context.”
-JCN
----- Original Message -----
From: “vlad-ntdev”
To: “NT Developers Interest List”
Sent: Sunday, March 17, 2002 6:22 AM
Subject: [ntdev] Re: TdiConnectionContext:
> The beginning of user connection context is at EaNameLength + 1 bytes in
> EaName buffer.
>
> FILE_FULL_EA_INFORMATION *ea = (FILE_FULL_EA_INFORMATION
> *)irp->AssociatedIrp.SystemBuffer;
>
> CONNECTION_CONTEXT conn_ctx = *(CONNECTION_CONTEXT *)(ea->EaName +
> ea->EaNameLength + 1);
>
> There’s no structure to represent it.
>
> vlad-ntdev
>
> ----- Original Message -----
> From: “Jonathan C. Nicklin”
> To: “NT Developers Interest List”
> Sent: Sunday, February 17, 2002 9:14 PM
> Subject: [ntdev] TdiConnectionContext:
>
>
> Ntdev,
> In the DDK documentation for a TDI client openning a connection
> endpoint, it says that the EaBuffer should contain contain an EaName
> member of TdiConnectionContext followed by “an EA value that is
> usually the address of a client allocated context area in which the =
> client
> will subsequently maintain state about the endpoint-to-endpoint =
> connection
> to be established.” What is this area and what structure respresents its
> data layout / how should it be allocated?
>
> Thanks,
> Jonathan Nicklin
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@verizon.net
> To unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@xetron.com
To unsubscribe send a blank email to %%email.unsub%%