Passing data from Wildcard application maps to ISAPI Filter

[Gaspar]

Is there any way to pass data from Wildcard application maps to ISAPI
Filter?
Right now, I'm passing data in the URL (I modify the URL with
HSE_REQ_EXEC_URL and then ISAPI filters sees the modified version) but I
don't want this data to arrive to the client browser.

Is there any server procedure, ECB property, etc.?
Thanks!

[David Wang]

IIS and ISAPI has no built-in support to share data between ISAPI
Filter and Extension.

Why don't you just pass a shared memory address between wildcard
application mapping and ISAPI Filter as the "data". This allows both
ISAPI Filter and wildcard application mapping to easily share data
without anything showing in the request/response nor client.

If you see this data going back to the client, then either you are
doing something seriously wrong, or the observed behavior is expected.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Post by Gaspar
Is there any way to pass data from Wildcard application maps to ISAPI
Filter?
Right now, I'm passing data in the URL (I modify the URL with
HSE_REQ_EXEC_URL and then ISAPI filters sees the modified version) but I
don't want this data to arrive to the client browser.
Is there any server procedure, ECB property, etc.?
Thanks!

[Gaspar]

Post by David Wang
IIS and ISAPI has no built-in support to share data between ISAPI
Filter and Extension.
Why don't you just pass a shared memory address between wildcard
application mapping and ISAPI Filter as the "data". This allows both
ISAPI Filter and wildcard application mapping to easily share data
without anything showing in the request/response nor client.
If you see this data going back to the client, then either you are
doing something seriously wrong, or the observed behavior is expected.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Post by Gaspar
Is there any way to pass data from Wildcard application maps to ISAPI
Filter?
Right now, I'm passing data in the URL (I modify the URL with
HSE_REQ_EXEC_URL and then ISAPI filters sees the modified version) but I
don't want this data to arrive to the client browser.
Is there any server procedure, ECB property, etc.?
Thanks!

It sounds well, but this will make my code very complicated.


Does IIS in any way identify user request with a unique ID?
I tried using the ECB.ConnID but (I don't know why) Wildcard App Map's
ConnId is different from Filter's ConnID in the same request.

Thanks again!

[David Wang]

Post by Gaspar

Post by David Wang
IIS and ISAPI has no built-in support to share data between ISAPI
Filter and Extension.
Why don't you just pass a shared memory address between wildcard
application mapping and ISAPI Filter as the "data". This allows both
ISAPI Filter and wildcard application mapping to easily share data
without anything showing in the request/response nor client.
If you see this data going back to the client, then either you are
doing something seriously wrong, or the observed behavior is expected.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Post by Gaspar
Is there any way to pass data from Wildcard application maps to ISAPI
Filter?
Right now, I'm passing data in the URL (I modify the URL with
HSE_REQ_EXEC_URL and then ISAPI filters sees the modified version) but I
don't want this data to arrive to the client browser.
Is there any server procedure, ECB property, etc.?
Thanks!

It sounds well, but this will make my code very complicated.
Does IIS in any way identify user request with a unique ID?
I tried using the ECB.ConnID but (I don't know why) Wildcard App Map's
ConnId is different from Filter's ConnID in the same request.
Thanks again!- Hide quoted text -
- Show quoted text -

ISAPI provides no explicit support to uniquely identify users,
sessions, nor user requests. ISAPI operates at the HTTP layer, and all
those concepts are application-layer concepts, which can be built on
top of ISAPI, but you have to do that work.

What I am suggesting is no more complicated than what you are
currently doing.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//