It seems you still want to keep things very transactional - even at this
higher (application level).
You could make the client so that it sends a response back to the server
when it has acknowledged what you sent.. so:
Caller->Server: "Gimme data"
Server: AddFilter
Server->Caller: Return "data"
Caller->Server: Ack Data - thanks!
Server. RemoveFilter
What about that?
"NET_NET_2003" <> wrote in message
news: om...
> first, thanx for ur participation 
>
> I have a DLL, with which I can create filters in my network card to
> perform some tasks on the packets leaving.
> When a request arrives to my Web Service,the Web Service(or Module, or
> somebody else) calls the "Create_filter" function of this DLL, and
> after the request has been sent, Web Service (or Module, or somebody
> else) must remove this filter calling "Remove_filter" function of the
> DLL.
>
> Creating is no problem (event BeginRequest), but I can't remove the
> filter when the event EndRequest is fired because the stream is still
> in the above layer, i.e. data has not been (maybe not compeletly)
> sent. I need to know, that data is out.
>
> Thanx
>
>
> "Frank Drebin" <> wrote in message
news:<h1p2b.33064$ igy.com>...
> > I'm not clear on what you said, let me see if I can recap:
> >
> > -a client attaches to your webservice
> > -the web service returns data
> > -you need to do something useful when the web service finishes returning
the
> > data?
> >
> > If so - in the WebMethod, why not put your code in there?
> >
> > "NET_NET_2003" <> wrote in message
> > news: ...