Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
inet
active_desktop
active_scrptng
asp.components
asp.db
asp.general
comctl32
comp.packaging
components.dev
dbweb
dhtml_editing
docobjects
html_authoring
html_objmodel
iis
iis.ftp
iis.security
iis.smtp_nntp
indexserver
misc
mshtml_hosting
scripting.jscript
scripting.vbscript
sdk_setup
shell_objmodel
urlmonikers
webbrowser_ctl
wininet
  
 
date: Sun, 10 Feb 2008 15:20:51 -0800 (PST),    group: microsoft.public.inetsdk.programming.urlmonikers        back       


Asynchronous Pluggable Protocol and synchronous opperation   
Hi all!

Sorry for my bad English :-((

What i must to do in Asynchronous Pluggable Protocol, if in the method
IInternetProtocolRoot::Start, call

pOIBindInfo->GetBindInfo(grfBINDF, pbindinfo);  doe's not have
BINDF_ASYNCHRONOUS flag


Please help my
date: Sun, 10 Feb 2008 15:20:51 -0800 (PST)   author:   unknown

Re: Asynchronous Pluggable Protocol and synchronous opperation   
wrote in message
news:e1d4ff14-00b9-4e01-9a40-7b9a16e47fe9@i12g2000prf.googlegroups.com
> What i must to do in Asynchronous Pluggable Protocol, if in the method
> IInternetProtocolRoot::Start, call
>
> pOIBindInfo->GetBindInfo(grfBINDF, pbindinfo);  doe's not have
> BINDF_ASYNCHRONOUS flag

You don't have control over this. The client chooses how it wants to 
perform the request. The APP should just do what the client tells it to.

However, an APP can just ignore BINDF_ASYNCHRONOUS flag and respond 
synchronously. The opposite is not true: if BINDF_ASYNCHRONOUS flag is 
_not_ specified, the APP must work synchronously, that is, report all 
the data before returning from Start (or else, return an error from 
Start call).
-- 
With best wishes,
    Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not 
necessarily a good idea. It is hard to be sure where they are going to 
land, and it could be dangerous sitting under them as they fly 
overhead. -- RFC 1925
date: Sun, 10 Feb 2008 18:46:44 -0500   author:   Igor Tandetnik

Re: Asynchronous Pluggable Protocol and synchronous opperation   
OK, but why URLOpenBlockingStream on standard http protocol return
S_OK, and on my protocol return E_FAIL??? I saw in debugger that
sequence of requests in my protocol and in standard http protocol
equivalent. Unfortunately in my protocol some thing wrong happened
date: Mon, 11 Feb 2008 00:38:28 -0800 (PST)   author:   unknown

Re: Asynchronous Pluggable Protocol and synchronous opperation   
wrote in message
news:68434388-3ec9-4742-9fcd-e68195c60106@l16g2000hsh.googlegroups.com
> OK, but why URLOpenBlockingStream on standard http protocol return
> S_OK, and on my protocol return E_FAIL???

You must be doing something wrong.

If you have a sample that reproduces the problem, you can send it to me 
at itandetnik@mvps.org, I'll look at it.
-- 
With best wishes,
    Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not 
necessarily a good idea. It is hard to be sure where they are going to 
land, and it could be dangerous sitting under them as they fly 
overhead. -- RFC 1925
date: Mon, 11 Feb 2008 07:34:14 -0500   author:   Igor Tandetnik

Re: Asynchronous Pluggable Protocol and synchronous opperation   
Thank you for preparedness to help
I'm sending my test project to your mail
date: Mon, 11 Feb 2008 10:51:55 -0800 (PST)   author:   unknown

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us