Server 2 Server http calls....Update


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 8 of 8

Thread: Server 2 Server http calls....Update

Hybrid View

  1. #1
    Paul Guest

    Server 2 Server http calls....Update


    An update on the issue:
    I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll internally.
    When I built an Standard Exe test harness to test my RemSvrInt.dll and deployed
    it onto my NT Server box it ran OK. I was able to create an MSXML2.XMLHTTP30
    object and call the send method posting a string to it. (It failed a few
    times).

    Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX DLL
    that is created by IIS. When a call was made to my RemSvrInt.dll it failed
    on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    failed. Being ActiveX dll they are running in the IIS server process which
    it doesn't seem to like one bit.

    Conclusions:
    1: Server 2 Server calls work sporadically
    2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    process (btw - this is on a client machine which is using PWS and doesn't
    have NT Server security!)

    Anyone have any thoughts?

    Thanks
    P.

    "Paul" <pfarnan@ireland.com> wrote:
    >
    >John,
    >I have installed an application on my server and was calling another server
    >and sometimes it stalled on the send (there could be other reasons) but

    the
    >following link explains its limitations(just in case you weren't aware).
    >I haven't benchedmarked the behaviour of it yet (It does work sporadically).
    >
    >http://support.microsoft.com/support.../q237/9/06.asp
    >I'm using this call inside an activeX dll - apartment threaded.
    >
    >Also when you say WININET does support server to server, what do you mean?
    >The following link states that the Win32 Internet functions do not support
    >server implementations and should not be used from a service.
    >http://msdn.microsoft.com/workshop/n...et/wininet.asp
    >
    >As an aside. Did you have problems installing the MSXML3 on your machine.
    >When I downloaded it and ran the install alongside previous version .exe
    >which allows it to run with previous versions(I had msxml v1) the entries
    >it placed in the registry and the progIDs seemed different. In VB when I
    >had
    >set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    >When I was building a dll I replaced new with CreateObject, it failed as
    >the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a reason/explanation
    >for this?
    >
    >I'm looking at programming sockets for the request which I was hoping to
    >avoid....(hands dirty time !)
    >
    >Thanks for your reply..
    >
    >Paul
    >
    >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>Ive never had any problems getting the xml http object to work for server

    >to
    >>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if your
    >>using it from VB (off the cuff guess so I could have a number out) - the
    >>object is free threaded so should be suitable for VB. Alternatively


    > you
    >>can use good old apartment threading with a reference to
    >>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not believe
    >>the object uses wiinet at all so you should have no problems.
    >>
    >>Although the wiinet api does supprt server to server, you can not
    >>efficiently use winnet api from vb as you seem to be aware unless its a

    >vb
    >>client not a dll from asp due to threading problems with vb, if you cant

    >use
    >>a third party compnent then use a socket to the remote servers port 80

    and
    >>issue http commands direct to the port, or use java if you know the
    >>language.
    >>
    >>--
    >>Regards
    >>
    >>John Timney
    >>Microsoft MVP
    >>(http://support.microsoft.com/support/mvp/program.asp)
    >>Co-Author Professional JSP
    >>ISBN: 1-861003-62-5
    >>
    >>
    >>
    >>Paul <pfarnan@ireland.com> wrote in message news:39b3777a$1@news.devx.com...
    >>>
    >>> I'm trying to send a http request server to server. All I want to do

    is
    >>post
    >>> to an ASP page, get a response back and do some action based on the

    >>response...
    >>> Its looking pretty grim at the minute. I've tried 2 approaches.
    >>> 1. Using the MSXML object but this doesn't support server 2 server and

    >>hangs
    >>> on the httprequest.send( ) method
    >>> 2. The WININET API which also doesn't support server 2 server
    >>>
    >>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason

    >for
    >>> its limitations.
    >>>
    >>> I'm using VB6.
    >>>
    >>> Can anyone point me in another direction.
    >>> I need to get this done ASAP
    >>>
    >>>
    >>> Thanks
    >>> Paul
    >>>

    >>
    >>

    >



  2. #2
    John Timney (MVP) Guest

    Re: Server 2 Server http calls....Update

    Paul,

    Sorry for the delay in replying, you might be getting a bit too deep in your
    solution when easier approaches could be available. Can I suggest you look
    up Alex Homer at www.asptoday.com, he has an excellent article that covers
    server side xmlhttp.

    --
    Regards

    John Timney
    Microsoft MVP
    (http://support.microsoft.com/support/mvp/program.asp)
    Co-Author Professional JSP
    ISBN: 1-861003-62-5



    Paul <pfarnan@ireland.com> wrote in message news:39b51215$1@news.devx.com...

    An update on the issue:
    I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    internally.
    When I built an Standard Exe test harness to test my RemSvrInt.dll and
    deployed
    it onto my NT Server box it ran OK. I was able to create an MSXML2.XMLHTTP30
    object and call the send method posting a string to it. (It failed a few
    times).

    Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX DLL
    that is created by IIS. When a call was made to my RemSvrInt.dll it failed
    on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    failed. Being ActiveX dll they are running in the IIS server process which
    it doesn't seem to like one bit.

    Conclusions:
    1: Server 2 Server calls work sporadically
    2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    process (btw - this is on a client machine which is using PWS and doesn't
    have NT Server security!)

    Anyone have any thoughts?

    Thanks
    P.

    "Paul" <pfarnan@ireland.com> wrote:
    >
    >John,
    >I have installed an application on my server and was calling another server
    >and sometimes it stalled on the send (there could be other reasons) but

    the
    >following link explains its limitations(just in case you weren't aware).
    >I haven't benchedmarked the behaviour of it yet (It does work

    sporadically).
    >
    >http://support.microsoft.com/support.../q237/9/06.asp
    >I'm using this call inside an activeX dll - apartment threaded.
    >
    >Also when you say WININET does support server to server, what do you mean?
    >The following link states that the Win32 Internet functions do not support
    >server implementations and should not be used from a service.
    >http://msdn.microsoft.com/workshop/n...et/wininet.asp
    >
    >As an aside. Did you have problems installing the MSXML3 on your machine.
    >When I downloaded it and ran the install alongside previous version .exe
    >which allows it to run with previous versions(I had msxml v1) the entries
    >it placed in the registry and the progIDs seemed different. In VB when I
    >had
    >set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    >When I was building a dll I replaced new with CreateObject, it failed as
    >the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a

    reason/explanation
    >for this?
    >
    >I'm looking at programming sockets for the request which I was hoping to
    >avoid....(hands dirty time !)
    >
    >Thanks for your reply..
    >
    >Paul
    >
    >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>Ive never had any problems getting the xml http object to work for server

    >to
    >>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if your
    >>using it from VB (off the cuff guess so I could have a number out) - the
    >>object is free threaded so should be suitable for VB. Alternatively


    > you
    >>can use good old apartment threading with a reference to
    >>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not believe
    >>the object uses wiinet at all so you should have no problems.
    >>
    >>Although the wiinet api does supprt server to server, you can not
    >>efficiently use winnet api from vb as you seem to be aware unless its a

    >vb
    >>client not a dll from asp due to threading problems with vb, if you cant

    >use
    >>a third party compnent then use a socket to the remote servers port 80

    and
    >>issue http commands direct to the port, or use java if you know the
    >>language.
    >>
    >>--
    >>Regards
    >>
    >>John Timney
    >>Microsoft MVP
    >>(http://support.microsoft.com/support/mvp/program.asp)
    >>Co-Author Professional JSP
    >>ISBN: 1-861003-62-5
    >>
    >>
    >>
    >>Paul <pfarnan@ireland.com> wrote in message

    news:39b3777a$1@news.devx.com...
    >>>
    >>> I'm trying to send a http request server to server. All I want to do

    is
    >>post
    >>> to an ASP page, get a response back and do some action based on the

    >>response...
    >>> Its looking pretty grim at the minute. I've tried 2 approaches.
    >>> 1. Using the MSXML object but this doesn't support server 2 server and

    >>hangs
    >>> on the httprequest.send( ) method
    >>> 2. The WININET API which also doesn't support server 2 server
    >>>
    >>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason

    >for
    >>> its limitations.
    >>>
    >>> I'm using VB6.
    >>>
    >>> Can anyone point me in another direction.
    >>> I need to get this done ASAP
    >>>
    >>>
    >>> Thanks
    >>> Paul
    >>>

    >>
    >>

    >





  3. #3
    paul Guest

    Re: Server 2 Server http calls....Update


    John,

    Thanks for the reply.
    I've read Alex's article on asptoday, which was the reason I was using XMLHTTP.
    Great article and things seem simple but unfortunatley a bit more complicated
    in practice. XMLHTTP doesn't support server 2 server communication. Looks
    like the only way is to write commands to the winsock dll directly. One alternative
    solution is a 3rd party component from serverobjects (www.serverobject.com)
    but this doesn't support secure communication.

    Thanks

    Paul


    "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >Paul,
    >
    >Sorry for the delay in replying, you might be getting a bit too deep in

    your
    >solution when easier approaches could be available. Can I suggest you

    look
    >up Alex Homer at www.asptoday.com, he has an excellent article that covers
    >server side xmlhttp.
    >
    >--
    >Regards
    >
    >John Timney
    >Microsoft MVP
    >(http://support.microsoft.com/support/mvp/program.asp)
    >Co-Author Professional JSP
    >ISBN: 1-861003-62-5
    >
    >
    >
    >Paul <pfarnan@ireland.com> wrote in message news:39b51215$1@news.devx.com...
    >
    >An update on the issue:
    >I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    >internally.
    >When I built an Standard Exe test harness to test my RemSvrInt.dll and
    >deployed
    >it onto my NT Server box it ran OK. I was able to create an MSXML2.XMLHTTP30
    >object and call the send method posting a string to it. (It failed a few
    >times).
    >
    >Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX

    DLL
    >that is created by IIS. When a call was made to my RemSvrInt.dll it failed
    >on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    >failed. Being ActiveX dll they are running in the IIS server process which
    >it doesn't seem to like one bit.
    >
    >Conclusions:
    >1: Server 2 Server calls work sporadically
    >2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    >process (btw - this is on a client machine which is using PWS and doesn't
    >have NT Server security!)
    >
    >Anyone have any thoughts?
    >
    >Thanks
    >P.
    >
    >"Paul" <pfarnan@ireland.com> wrote:
    >>
    >>John,
    >>I have installed an application on my server and was calling another server
    >>and sometimes it stalled on the send (there could be other reasons) but

    >the
    >>following link explains its limitations(just in case you weren't aware).
    >>I haven't benchedmarked the behaviour of it yet (It does work

    >sporadically).
    >>
    >>http://support.microsoft.com/support.../q237/9/06.asp
    >>I'm using this call inside an activeX dll - apartment threaded.
    >>
    >>Also when you say WININET does support server to server, what do you mean?
    >>The following link states that the Win32 Internet functions do not support
    >>server implementations and should not be used from a service.
    >>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    >>
    >>As an aside. Did you have problems installing the MSXML3 on your machine.
    >>When I downloaded it and ran the install alongside previous version .exe
    >>which allows it to run with previous versions(I had msxml v1) the entries
    >>it placed in the registry and the progIDs seemed different. In VB when

    I
    >>had
    >>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    >>When I was building a dll I replaced new with CreateObject, it failed as
    >>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a

    >reason/explanation
    >>for this?
    >>
    >>I'm looking at programming sockets for the request which I was hoping to
    >>avoid....(hands dirty time !)
    >>
    >>Thanks for your reply..
    >>
    >>Paul
    >>
    >>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>>Ive never had any problems getting the xml http object to work for server

    >>to
    >>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if

    your
    >>>using it from VB (off the cuff guess so I could have a number out) -

    the
    >>>object is free threaded so should be suitable for VB. Alternatively

    >
    >> you
    >>>can use good old apartment threading with a reference to
    >>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not believe
    >>>the object uses wiinet at all so you should have no problems.
    >>>
    >>>Although the wiinet api does supprt server to server, you can not
    >>>efficiently use winnet api from vb as you seem to be aware unless its

    a
    >>vb
    >>>client not a dll from asp due to threading problems with vb, if you cant

    >>use
    >>>a third party compnent then use a socket to the remote servers port 80

    >and
    >>>issue http commands direct to the port, or use java if you know the
    >>>language.
    >>>
    >>>--
    >>>Regards
    >>>
    >>>John Timney
    >>>Microsoft MVP
    >>>(http://support.microsoft.com/support/mvp/program.asp)
    >>>Co-Author Professional JSP
    >>>ISBN: 1-861003-62-5
    >>>
    >>>
    >>>
    >>>Paul <pfarnan@ireland.com> wrote in message

    >news:39b3777a$1@news.devx.com...
    >>>>
    >>>> I'm trying to send a http request server to server. All I want to do

    >is
    >>>post
    >>>> to an ASP page, get a response back and do some action based on the
    >>>response...
    >>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    >>>> 1. Using the MSXML object but this doesn't support server 2 server and
    >>>hangs
    >>>> on the httprequest.send( ) method
    >>>> 2. The WININET API which also doesn't support server 2 server
    >>>>
    >>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason

    >>for
    >>>> its limitations.
    >>>>
    >>>> I'm using VB6.
    >>>>
    >>>> Can anyone point me in another direction.
    >>>> I need to get this done ASAP
    >>>>
    >>>>
    >>>> Thanks
    >>>> Paul
    >>>>
    >>>
    >>>

    >>

    >
    >
    >



  4. #4
    John Timney (MVP) Guest

    Re: Server 2 Server http calls....Update

    Tom,

    I use the xmlhttp object to get asp to talk to another server through a
    proxy (hence server to server coms) ... is this what your after. I'm not
    even sure if it handles ssl - I would guess not though.

    If not, I can tell you the code for winsock is not easy to do, the api is
    very complicated - and from VB its a bit of a nightmare and ssl will add to
    those complications, I have an example in VB you could have if it will help
    but it has no ssl support - you would need to add that.
    --
    Regards

    John Timney
    Microsoft MVP
    (http://support.microsoft.com/support/mvp/program.asp)
    Co-Author Professional JSP
    ISBN: 1-861003-62-5



    paul <pfarnan@ireland.com> wrote in message news:39bf5217$1@news.devx.com...

    John,

    Thanks for the reply.
    I've read Alex's article on asptoday, which was the reason I was using
    XMLHTTP.
    Great article and things seem simple but unfortunatley a bit more
    complicated
    in practice. XMLHTTP doesn't support server 2 server communication. Looks
    like the only way is to write commands to the winsock dll directly. One
    alternative
    solution is a 3rd party component from serverobjects (www.serverobject.com)
    but this doesn't support secure communication.

    Thanks

    Paul


    "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >Paul,
    >
    >Sorry for the delay in replying, you might be getting a bit too deep in

    your
    >solution when easier approaches could be available. Can I suggest you

    look
    >up Alex Homer at www.asptoday.com, he has an excellent article that covers
    >server side xmlhttp.
    >
    >--
    >Regards
    >
    >John Timney
    >Microsoft MVP
    >(http://support.microsoft.com/support/mvp/program.asp)
    >Co-Author Professional JSP
    >ISBN: 1-861003-62-5
    >
    >
    >
    >Paul <pfarnan@ireland.com> wrote in message

    news:39b51215$1@news.devx.com...
    >
    >An update on the issue:
    >I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    >internally.
    >When I built an Standard Exe test harness to test my RemSvrInt.dll and
    >deployed
    >it onto my NT Server box it ran OK. I was able to create an

    MSXML2.XMLHTTP30
    >object and call the send method posting a string to it. (It failed a few
    >times).
    >
    >Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX

    DLL
    >that is created by IIS. When a call was made to my RemSvrInt.dll it failed
    >on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    >failed. Being ActiveX dll they are running in the IIS server process which
    >it doesn't seem to like one bit.
    >
    >Conclusions:
    >1: Server 2 Server calls work sporadically
    >2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    >process (btw - this is on a client machine which is using PWS and doesn't
    >have NT Server security!)
    >
    >Anyone have any thoughts?
    >
    >Thanks
    >P.
    >
    >"Paul" <pfarnan@ireland.com> wrote:
    >>
    >>John,
    >>I have installed an application on my server and was calling another

    server
    >>and sometimes it stalled on the send (there could be other reasons) but

    >the
    >>following link explains its limitations(just in case you weren't aware).
    >>I haven't benchedmarked the behaviour of it yet (It does work

    >sporadically).
    >>
    >>http://support.microsoft.com/support.../q237/9/06.asp
    >>I'm using this call inside an activeX dll - apartment threaded.
    >>
    >>Also when you say WININET does support server to server, what do you mean?
    >>The following link states that the Win32 Internet functions do not support
    >>server implementations and should not be used from a service.
    >>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    >>
    >>As an aside. Did you have problems installing the MSXML3 on your machine.
    >>When I downloaded it and ran the install alongside previous version .exe
    >>which allows it to run with previous versions(I had msxml v1) the entries
    >>it placed in the registry and the progIDs seemed different. In VB when

    I
    >>had
    >>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    >>When I was building a dll I replaced new with CreateObject, it failed as
    >>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a

    >reason/explanation
    >>for this?
    >>
    >>I'm looking at programming sockets for the request which I was hoping to
    >>avoid....(hands dirty time !)
    >>
    >>Thanks for your reply..
    >>
    >>Paul
    >>
    >>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>>Ive never had any problems getting the xml http object to work for server

    >>to
    >>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if

    your
    >>>using it from VB (off the cuff guess so I could have a number out) -

    the
    >>>object is free threaded so should be suitable for VB. Alternatively

    >
    >> you
    >>>can use good old apartment threading with a reference to
    >>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not

    believe
    >>>the object uses wiinet at all so you should have no problems.
    >>>
    >>>Although the wiinet api does supprt server to server, you can not
    >>>efficiently use winnet api from vb as you seem to be aware unless its

    a
    >>vb
    >>>client not a dll from asp due to threading problems with vb, if you cant

    >>use
    >>>a third party compnent then use a socket to the remote servers port 80

    >and
    >>>issue http commands direct to the port, or use java if you know the
    >>>language.
    >>>
    >>>--
    >>>Regards
    >>>
    >>>John Timney
    >>>Microsoft MVP
    >>>(http://support.microsoft.com/support/mvp/program.asp)
    >>>Co-Author Professional JSP
    >>>ISBN: 1-861003-62-5
    >>>
    >>>
    >>>
    >>>Paul <pfarnan@ireland.com> wrote in message

    >news:39b3777a$1@news.devx.com...
    >>>>
    >>>> I'm trying to send a http request server to server. All I want to do

    >is
    >>>post
    >>>> to an ASP page, get a response back and do some action based on the
    >>>response...
    >>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    >>>> 1. Using the MSXML object but this doesn't support server 2 server and
    >>>hangs
    >>>> on the httprequest.send( ) method
    >>>> 2. The WININET API which also doesn't support server 2 server
    >>>>
    >>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason

    >>for
    >>>> its limitations.
    >>>>
    >>>> I'm using VB6.
    >>>>
    >>>> Can anyone point me in another direction.
    >>>> I need to get this done ASAP
    >>>>
    >>>>
    >>>> Thanks
    >>>> Paul
    >>>>
    >>>
    >>>

    >>

    >
    >
    >





  5. #5
    Paul Guest

    Re: Server 2 Server http calls....Update


    John,

    Thanks for that. I have some simple winsock code here that I was looking
    through and came to the same conclusion about the difficulties involved so
    I went with the 3rd party solution which we have deployed and is communicating
    across servers fine. Just not https.
    They are soon to update their documentation on XMLHTTP now to read:

    "NOTE: While this article mainly attends to the use of XMLHttpRequest from
    ASP or ISAPI code, this problem actually applies to ANY server-to-server
    usage of XMLHttpRequest from any kind of codebase. At the most basic level,
    there is currently no supported method for sending HTTP-based requests between
    HTTP servers and any technique -- XMLHttpRequest or otherwise -- that is
    not restricted to a client machine sending the request to a server will experience
    unforeseen problems."

    I'm looking into using java objects for the http communication and wrapping
    them as COM objects.

    Thanks
    Paul.


    "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >Tom,
    >
    >I use the xmlhttp object to get asp to talk to another server through a
    >proxy (hence server to server coms) ... is this what your after. I'm not
    >even sure if it handles ssl - I would guess not though.
    >
    >If not, I can tell you the code for winsock is not easy to do, the api is
    >very complicated - and from VB its a bit of a nightmare and ssl will add

    to
    >those complications, I have an example in VB you could have if it will help
    >but it has no ssl support - you would need to add that.
    >--
    >Regards
    >
    >John Timney
    >Microsoft MVP
    >(http://support.microsoft.com/support/mvp/program.asp)
    >Co-Author Professional JSP
    >ISBN: 1-861003-62-5
    >
    >
    >
    >paul <pfarnan@ireland.com> wrote in message news:39bf5217$1@news.devx.com...
    >
    >John,
    >
    >Thanks for the reply.
    >I've read Alex's article on asptoday, which was the reason I was using
    >XMLHTTP.
    >Great article and things seem simple but unfortunatley a bit more
    >complicated
    >in practice. XMLHTTP doesn't support server 2 server communication. Looks
    >like the only way is to write commands to the winsock dll directly. One
    >alternative
    >solution is a 3rd party component from serverobjects (www.serverobject.com)
    >but this doesn't support secure communication.
    >
    >Thanks
    >
    >Paul
    >
    >
    >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>Paul,
    >>
    >>Sorry for the delay in replying, you might be getting a bit too deep in

    >your
    >>solution when easier approaches could be available. Can I suggest you

    >look
    >>up Alex Homer at www.asptoday.com, he has an excellent article that covers
    >>server side xmlhttp.
    >>
    >>--
    >>Regards
    >>
    >>John Timney
    >>Microsoft MVP
    >>(http://support.microsoft.com/support/mvp/program.asp)
    >>Co-Author Professional JSP
    >>ISBN: 1-861003-62-5
    >>
    >>
    >>
    >>Paul <pfarnan@ireland.com> wrote in message

    >news:39b51215$1@news.devx.com...
    >>
    >>An update on the issue:
    >>I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    >>internally.
    >>When I built an Standard Exe test harness to test my RemSvrInt.dll and
    >>deployed
    >>it onto my NT Server box it ran OK. I was able to create an

    >MSXML2.XMLHTTP30
    >>object and call the send method posting a string to it. (It failed a few
    >>times).
    >>
    >>Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX

    >DLL
    >>that is created by IIS. When a call was made to my RemSvrInt.dll it failed
    >>on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    >>failed. Being ActiveX dll they are running in the IIS server process which
    >>it doesn't seem to like one bit.
    >>
    >>Conclusions:
    >>1: Server 2 Server calls work sporadically
    >>2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    >>process (btw - this is on a client machine which is using PWS and doesn't
    >>have NT Server security!)
    >>
    >>Anyone have any thoughts?
    >>
    >>Thanks
    >>P.
    >>
    >>"Paul" <pfarnan@ireland.com> wrote:
    >>>
    >>>John,
    >>>I have installed an application on my server and was calling another

    >server
    >>>and sometimes it stalled on the send (there could be other reasons) but

    >>the
    >>>following link explains its limitations(just in case you weren't aware).
    >>>I haven't benchedmarked the behaviour of it yet (It does work

    >>sporadically).
    >>>
    >>>http://support.microsoft.com/support.../q237/9/06.asp
    >>>I'm using this call inside an activeX dll - apartment threaded.
    >>>
    >>>Also when you say WININET does support server to server, what do you mean?
    >>>The following link states that the Win32 Internet functions do not support
    >>>server implementations and should not be used from a service.
    >>>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    >>>
    >>>As an aside. Did you have problems installing the MSXML3 on your machine.
    >>>When I downloaded it and ran the install alongside previous version .exe
    >>>which allows it to run with previous versions(I had msxml v1) the entries
    >>>it placed in the registry and the progIDs seemed different. In VB when

    >I
    >>>had
    >>>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    >>>When I was building a dll I replaced new with CreateObject, it failed

    as
    >>>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a

    >>reason/explanation
    >>>for this?
    >>>
    >>>I'm looking at programming sockets for the request which I was hoping

    to
    >>>avoid....(hands dirty time !)
    >>>
    >>>Thanks for your reply..
    >>>
    >>>Paul
    >>>
    >>>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    >>>>Ive never had any problems getting the xml http object to work for server
    >>>to
    >>>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if

    >your
    >>>>using it from VB (off the cuff guess so I could have a number out) -

    >the
    >>>>object is free threaded so should be suitable for VB. Alternatively

    >>
    >>> you
    >>>>can use good old apartment threading with a reference to
    >>>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not

    >believe
    >>>>the object uses wiinet at all so you should have no problems.
    >>>>
    >>>>Although the wiinet api does supprt server to server, you can not
    >>>>efficiently use winnet api from vb as you seem to be aware unless its

    >a
    >>>vb
    >>>>client not a dll from asp due to threading problems with vb, if you cant
    >>>use
    >>>>a third party compnent then use a socket to the remote servers port 80

    >>and
    >>>>issue http commands direct to the port, or use java if you know the
    >>>>language.
    >>>>
    >>>>--
    >>>>Regards
    >>>>
    >>>>John Timney
    >>>>Microsoft MVP
    >>>>(http://support.microsoft.com/support/mvp/program.asp)
    >>>>Co-Author Professional JSP
    >>>>ISBN: 1-861003-62-5
    >>>>
    >>>>
    >>>>
    >>>>Paul <pfarnan@ireland.com> wrote in message

    >>news:39b3777a$1@news.devx.com...
    >>>>>
    >>>>> I'm trying to send a http request server to server. All I want to do

    >>is
    >>>>post
    >>>>> to an ASP page, get a response back and do some action based on the
    >>>>response...
    >>>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    >>>>> 1. Using the MSXML object but this doesn't support server 2 server

    and
    >>>>hangs
    >>>>> on the httprequest.send( ) method
    >>>>> 2. The WININET API which also doesn't support server 2 server
    >>>>>
    >>>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason
    >>>for
    >>>>> its limitations.
    >>>>>
    >>>>> I'm using VB6.
    >>>>>
    >>>>> Can anyone point me in another direction.
    >>>>> I need to get this done ASAP
    >>>>>
    >>>>>
    >>>>> Thanks
    >>>>> Paul
    >>>>>
    >>>>
    >>>>
    >>>

    >>
    >>
    >>

    >
    >
    >



  6. #6
    Chris Kinsman Guest

    Re: Server 2 Server http calls....Update

    A friend of mine just switched to a new COM component that does not use
    WinInet and eliminated most of the problems he was having with this
    technique. I believe he is currently using the Mabry com object for this.

    "Paul" <pfarnan@ireland.com> wrote in message news:39c0b6a9@news.devx.com...
    >
    > John,
    >
    > Thanks for that. I have some simple winsock code here that I was looking
    > through and came to the same conclusion about the difficulties involved so
    > I went with the 3rd party solution which we have deployed and is

    communicating
    > across servers fine. Just not https.
    > They are soon to update their documentation on XMLHTTP now to read:
    >
    > "NOTE: While this article mainly attends to the use of XMLHttpRequest from
    > ASP or ISAPI code, this problem actually applies to ANY server-to-server
    > usage of XMLHttpRequest from any kind of codebase. At the most basic

    level,
    > there is currently no supported method for sending HTTP-based requests

    between
    > HTTP servers and any technique -- XMLHttpRequest or otherwise -- that is
    > not restricted to a client machine sending the request to a server will

    experience
    > unforeseen problems."
    >
    > I'm looking into using java objects for the http communication and

    wrapping
    > them as COM objects.
    >
    > Thanks
    > Paul.
    >
    >
    > "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >Tom,
    > >
    > >I use the xmlhttp object to get asp to talk to another server through a
    > >proxy (hence server to server coms) ... is this what your after. I'm not
    > >even sure if it handles ssl - I would guess not though.
    > >
    > >If not, I can tell you the code for winsock is not easy to do, the api is
    > >very complicated - and from VB its a bit of a nightmare and ssl will add

    > to
    > >those complications, I have an example in VB you could have if it will

    help
    > >but it has no ssl support - you would need to add that.
    > >--
    > >Regards
    > >
    > >John Timney
    > >Microsoft MVP
    > >(http://support.microsoft.com/support/mvp/program.asp)
    > >Co-Author Professional JSP
    > >ISBN: 1-861003-62-5
    > >
    > >
    > >
    > >paul <pfarnan@ireland.com> wrote in message

    news:39bf5217$1@news.devx.com...
    > >
    > >John,
    > >
    > >Thanks for the reply.
    > >I've read Alex's article on asptoday, which was the reason I was using
    > >XMLHTTP.
    > >Great article and things seem simple but unfortunatley a bit more
    > >complicated
    > >in practice. XMLHTTP doesn't support server 2 server communication. Looks
    > >like the only way is to write commands to the winsock dll directly. One
    > >alternative
    > >solution is a 3rd party component from serverobjects

    (www.serverobject.com)
    > >but this doesn't support secure communication.
    > >
    > >Thanks
    > >
    > >Paul
    > >
    > >
    > >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >>Paul,
    > >>
    > >>Sorry for the delay in replying, you might be getting a bit too deep in

    > >your
    > >>solution when easier approaches could be available. Can I suggest you

    > >look
    > >>up Alex Homer at www.asptoday.com, he has an excellent article that

    covers
    > >>server side xmlhttp.
    > >>
    > >>--
    > >>Regards
    > >>
    > >>John Timney
    > >>Microsoft MVP
    > >>(http://support.microsoft.com/support/mvp/program.asp)
    > >>Co-Author Professional JSP
    > >>ISBN: 1-861003-62-5
    > >>
    > >>
    > >>
    > >>Paul <pfarnan@ireland.com> wrote in message

    > >news:39b51215$1@news.devx.com...
    > >>
    > >>An update on the issue:
    > >>I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    > >>internally.
    > >>When I built an Standard Exe test harness to test my RemSvrInt.dll and
    > >>deployed
    > >>it onto my NT Server box it ran OK. I was able to create an

    > >MSXML2.XMLHTTP30
    > >>object and call the send method posting a string to it. (It failed a few
    > >>times).
    > >>
    > >>Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX

    > >DLL
    > >>that is created by IIS. When a call was made to my RemSvrInt.dll it

    failed
    > >>on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    > >>failed. Being ActiveX dll they are running in the IIS server process

    which
    > >>it doesn't seem to like one bit.
    > >>
    > >>Conclusions:
    > >>1: Server 2 Server calls work sporadically
    > >>2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    > >>process (btw - this is on a client machine which is using PWS and

    doesn't
    > >>have NT Server security!)
    > >>
    > >>Anyone have any thoughts?
    > >>
    > >>Thanks
    > >>P.
    > >>
    > >>"Paul" <pfarnan@ireland.com> wrote:
    > >>>
    > >>>John,
    > >>>I have installed an application on my server and was calling another

    > >server
    > >>>and sometimes it stalled on the send (there could be other reasons) but
    > >>the
    > >>>following link explains its limitations(just in case you weren't

    aware).
    > >>>I haven't benchedmarked the behaviour of it yet (It does work
    > >>sporadically).
    > >>>
    > >>>http://support.microsoft.com/support.../q237/9/06.asp
    > >>>I'm using this call inside an activeX dll - apartment threaded.
    > >>>
    > >>>Also when you say WININET does support server to server, what do you

    mean?
    > >>>The following link states that the Win32 Internet functions do not

    support
    > >>>server implementations and should not be used from a service.
    > >>>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    > >>>
    > >>>As an aside. Did you have problems installing the MSXML3 on your

    machine.
    > >>>When I downloaded it and ran the install alongside previous version

    ..exe
    > >>>which allows it to run with previous versions(I had msxml v1) the

    entries
    > >>>it placed in the registry and the progIDs seemed different. In VB when

    > >I
    > >>>had
    > >>>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    > >>>When I was building a dll I replaced new with CreateObject, it failed

    > as
    > >>>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a
    > >>reason/explanation
    > >>>for this?
    > >>>
    > >>>I'm looking at programming sockets for the request which I was hoping

    > to
    > >>>avoid....(hands dirty time !)
    > >>>
    > >>>Thanks for your reply..
    > >>>
    > >>>Paul
    > >>>
    > >>>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >>>>Ive never had any problems getting the xml http object to work for

    server
    > >>>to
    > >>>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if

    > >your
    > >>>>using it from VB (off the cuff guess so I could have a number out) -

    > >the
    > >>>>object is free threaded so should be suitable for VB. Alternatively
    > >>
    > >>> you
    > >>>>can use good old apartment threading with a reference to
    > >>>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not

    > >believe
    > >>>>the object uses wiinet at all so you should have no problems.
    > >>>>
    > >>>>Although the wiinet api does supprt server to server, you can not
    > >>>>efficiently use winnet api from vb as you seem to be aware unless its

    > >a
    > >>>vb
    > >>>>client not a dll from asp due to threading problems with vb, if you

    cant
    > >>>use
    > >>>>a third party compnent then use a socket to the remote servers port 80
    > >>and
    > >>>>issue http commands direct to the port, or use java if you know the
    > >>>>language.
    > >>>>
    > >>>>--
    > >>>>Regards
    > >>>>
    > >>>>John Timney
    > >>>>Microsoft MVP
    > >>>>(http://support.microsoft.com/support/mvp/program.asp)
    > >>>>Co-Author Professional JSP
    > >>>>ISBN: 1-861003-62-5
    > >>>>
    > >>>>
    > >>>>
    > >>>>Paul <pfarnan@ireland.com> wrote in message
    > >>news:39b3777a$1@news.devx.com...
    > >>>>>
    > >>>>> I'm trying to send a http request server to server. All I want to do
    > >>is
    > >>>>post
    > >>>>> to an ASP page, get a response back and do some action based on the
    > >>>>response...
    > >>>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    > >>>>> 1. Using the MSXML object but this doesn't support server 2 server

    > and
    > >>>>hangs
    > >>>>> on the httprequest.send( ) method
    > >>>>> 2. The WININET API which also doesn't support server 2 server
    > >>>>>
    > >>>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the

    reason
    > >>>for
    > >>>>> its limitations.
    > >>>>>
    > >>>>> I'm using VB6.
    > >>>>>
    > >>>>> Can anyone point me in another direction.
    > >>>>> I need to get this done ASAP
    > >>>>>
    > >>>>>
    > >>>>> Thanks
    > >>>>> Paul
    > >>>>>
    > >>>>
    > >>>>
    > >>>
    > >>
    > >>
    > >>

    > >
    > >
    > >

    >




  7. #7
    John Timney (MVP) Guest

    Re: Server 2 Server http calls....Update

    there are a few good off the shelf options and the Mabry controls are well
    supported - personally I dont like not having the code, Incidentally, have
    you looked at Perl from asp, it might have the support you need without
    third party bits.

    I do a lot of this stuff with Java classes as com from asp, but not via
    https, its bad enough having to base64 encode it for proxy access - I would
    be keen to see how far you get with the ssl stuff.

    --
    Regards

    John Timney
    Microsoft MVP
    (http://support.microsoft.com/support/mvp/program.asp)
    Co-Author Professional JSP
    ISBN: 1-861003-62-5



    Chris Kinsman <ckinsman@devx.com> wrote in message
    news:39c0c239$1@news.devx.com...
    A friend of mine just switched to a new COM component that does not use
    WinInet and eliminated most of the problems he was having with this
    technique. I believe he is currently using the Mabry com object for this.

    "Paul" <pfarnan@ireland.com> wrote in message news:39c0b6a9@news.devx.com...
    >
    > John,
    >
    > Thanks for that. I have some simple winsock code here that I was looking
    > through and came to the same conclusion about the difficulties involved so
    > I went with the 3rd party solution which we have deployed and is

    communicating
    > across servers fine. Just not https.
    > They are soon to update their documentation on XMLHTTP now to read:
    >
    > "NOTE: While this article mainly attends to the use of XMLHttpRequest from
    > ASP or ISAPI code, this problem actually applies to ANY server-to-server
    > usage of XMLHttpRequest from any kind of codebase. At the most basic

    level,
    > there is currently no supported method for sending HTTP-based requests

    between
    > HTTP servers and any technique -- XMLHttpRequest or otherwise -- that is
    > not restricted to a client machine sending the request to a server will

    experience
    > unforeseen problems."
    >
    > I'm looking into using java objects for the http communication and

    wrapping
    > them as COM objects.
    >
    > Thanks
    > Paul.
    >
    >
    > "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >Tom,
    > >
    > >I use the xmlhttp object to get asp to talk to another server through a
    > >proxy (hence server to server coms) ... is this what your after. I'm not
    > >even sure if it handles ssl - I would guess not though.
    > >
    > >If not, I can tell you the code for winsock is not easy to do, the api is
    > >very complicated - and from VB its a bit of a nightmare and ssl will add

    > to
    > >those complications, I have an example in VB you could have if it will

    help
    > >but it has no ssl support - you would need to add that.
    > >--
    > >Regards
    > >
    > >John Timney
    > >Microsoft MVP
    > >(http://support.microsoft.com/support/mvp/program.asp)
    > >Co-Author Professional JSP
    > >ISBN: 1-861003-62-5
    > >
    > >
    > >
    > >paul <pfarnan@ireland.com> wrote in message

    news:39bf5217$1@news.devx.com...
    > >
    > >John,
    > >
    > >Thanks for the reply.
    > >I've read Alex's article on asptoday, which was the reason I was using
    > >XMLHTTP.
    > >Great article and things seem simple but unfortunatley a bit more
    > >complicated
    > >in practice. XMLHTTP doesn't support server 2 server communication. Looks
    > >like the only way is to write commands to the winsock dll directly. One
    > >alternative
    > >solution is a 3rd party component from serverobjects

    (www.serverobject.com)
    > >but this doesn't support secure communication.
    > >
    > >Thanks
    > >
    > >Paul
    > >
    > >
    > >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >>Paul,
    > >>
    > >>Sorry for the delay in replying, you might be getting a bit too deep in

    > >your
    > >>solution when easier approaches could be available. Can I suggest you

    > >look
    > >>up Alex Homer at www.asptoday.com, he has an excellent article that

    covers
    > >>server side xmlhttp.
    > >>
    > >>--
    > >>Regards
    > >>
    > >>John Timney
    > >>Microsoft MVP
    > >>(http://support.microsoft.com/support/mvp/program.asp)
    > >>Co-Author Professional JSP
    > >>ISBN: 1-861003-62-5
    > >>
    > >>
    > >>
    > >>Paul <pfarnan@ireland.com> wrote in message

    > >news:39b51215$1@news.devx.com...
    > >>
    > >>An update on the issue:
    > >>I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    > >>internally.
    > >>When I built an Standard Exe test harness to test my RemSvrInt.dll and
    > >>deployed
    > >>it onto my NT Server box it ran OK. I was able to create an

    > >MSXML2.XMLHTTP30
    > >>object and call the send method posting a string to it. (It failed a few
    > >>times).
    > >>
    > >>Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX

    > >DLL
    > >>that is created by IIS. When a call was made to my RemSvrInt.dll it

    failed
    > >>on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
    > >>failed. Being ActiveX dll they are running in the IIS server process

    which
    > >>it doesn't seem to like one bit.
    > >>
    > >>Conclusions:
    > >>1: Server 2 Server calls work sporadically
    > >>2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
    > >>process (btw - this is on a client machine which is using PWS and

    doesn't
    > >>have NT Server security!)
    > >>
    > >>Anyone have any thoughts?
    > >>
    > >>Thanks
    > >>P.
    > >>
    > >>"Paul" <pfarnan@ireland.com> wrote:
    > >>>
    > >>>John,
    > >>>I have installed an application on my server and was calling another

    > >server
    > >>>and sometimes it stalled on the send (there could be other reasons) but
    > >>the
    > >>>following link explains its limitations(just in case you weren't

    aware).
    > >>>I haven't benchedmarked the behaviour of it yet (It does work
    > >>sporadically).
    > >>>
    > >>>http://support.microsoft.com/support.../q237/9/06.asp
    > >>>I'm using this call inside an activeX dll - apartment threaded.
    > >>>
    > >>>Also when you say WININET does support server to server, what do you

    mean?
    > >>>The following link states that the Win32 Internet functions do not

    support
    > >>>server implementations and should not be used from a service.
    > >>>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    > >>>
    > >>>As an aside. Did you have problems installing the MSXML3 on your

    machine.
    > >>>When I downloaded it and ran the install alongside previous version

    ..exe
    > >>>which allows it to run with previous versions(I had msxml v1) the

    entries
    > >>>it placed in the registry and the progIDs seemed different. In VB when

    > >I
    > >>>had
    > >>>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    > >>>When I was building a dll I replaced new with CreateObject, it failed

    > as
    > >>>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a
    > >>reason/explanation
    > >>>for this?
    > >>>
    > >>>I'm looking at programming sockets for the request which I was hoping

    > to
    > >>>avoid....(hands dirty time !)
    > >>>
    > >>>Thanks for your reply..
    > >>>
    > >>>Paul
    > >>>
    > >>>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > >>>>Ive never had any problems getting the xml http object to work for

    server
    > >>>to
    > >>>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if

    > >your
    > >>>>using it from VB (off the cuff guess so I could have a number out) -

    > >the
    > >>>>object is free threaded so should be suitable for VB. Alternatively
    > >>
    > >>> you
    > >>>>can use good old apartment threading with a reference to
    > >>>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not

    > >believe
    > >>>>the object uses wiinet at all so you should have no problems.
    > >>>>
    > >>>>Although the wiinet api does supprt server to server, you can not
    > >>>>efficiently use winnet api from vb as you seem to be aware unless its

    > >a
    > >>>vb
    > >>>>client not a dll from asp due to threading problems with vb, if you

    cant
    > >>>use
    > >>>>a third party compnent then use a socket to the remote servers port 80
    > >>and
    > >>>>issue http commands direct to the port, or use java if you know the
    > >>>>language.
    > >>>>
    > >>>>--
    > >>>>Regards
    > >>>>
    > >>>>John Timney
    > >>>>Microsoft MVP
    > >>>>(http://support.microsoft.com/support/mvp/program.asp)
    > >>>>Co-Author Professional JSP
    > >>>>ISBN: 1-861003-62-5
    > >>>>
    > >>>>
    > >>>>
    > >>>>Paul <pfarnan@ireland.com> wrote in message
    > >>news:39b3777a$1@news.devx.com...
    > >>>>>
    > >>>>> I'm trying to send a http request server to server. All I want to do
    > >>is
    > >>>>post
    > >>>>> to an ASP page, get a response back and do some action based on the
    > >>>>response...
    > >>>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    > >>>>> 1. Using the MSXML object but this doesn't support server 2 server

    > and
    > >>>>hangs
    > >>>>> on the httprequest.send( ) method
    > >>>>> 2. The WININET API which also doesn't support server 2 server
    > >>>>>
    > >>>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the

    reason
    > >>>for
    > >>>>> its limitations.
    > >>>>>
    > >>>>> I'm using VB6.
    > >>>>>
    > >>>>> Can anyone point me in another direction.
    > >>>>> I need to get this done ASAP
    > >>>>>
    > >>>>>
    > >>>>> Thanks
    > >>>>> Paul
    > >>>>>
    > >>>>
    > >>>>
    > >>>
    > >>
    > >>
    > >>

    > >
    > >
    > >

    >






  8. #8
    Chris Kinsman Guest

    Re: Server 2 Server http calls....Update

    Mabry sells their source. No reason not to have it unless you don't want to
    pay for it or like implementing yourself...

    "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote in message
    news:39c10b1f@news.devx.com...
    > there are a few good off the shelf options and the Mabry controls are well
    > supported - personally I dont like not having the code, Incidentally,

    have
    > you looked at Perl from asp, it might have the support you need without
    > third party bits.
    >
    > I do a lot of this stuff with Java classes as com from asp, but not via
    > https, its bad enough having to base64 encode it for proxy access - I

    would
    > be keen to see how far you get with the ssl stuff.
    >
    > --
    > Regards
    >
    > John Timney
    > Microsoft MVP
    > (http://support.microsoft.com/support/mvp/program.asp)
    > Co-Author Professional JSP
    > ISBN: 1-861003-62-5
    >
    >
    >
    > Chris Kinsman <ckinsman@devx.com> wrote in message
    > news:39c0c239$1@news.devx.com...
    > A friend of mine just switched to a new COM component that does not use
    > WinInet and eliminated most of the problems he was having with this
    > technique. I believe he is currently using the Mabry com object for this.
    >
    > "Paul" <pfarnan@ireland.com> wrote in message

    news:39c0b6a9@news.devx.com...
    > >
    > > John,
    > >
    > > Thanks for that. I have some simple winsock code here that I was looking
    > > through and came to the same conclusion about the difficulties involved

    so
    > > I went with the 3rd party solution which we have deployed and is

    > communicating
    > > across servers fine. Just not https.
    > > They are soon to update their documentation on XMLHTTP now to read:
    > >
    > > "NOTE: While this article mainly attends to the use of XMLHttpRequest

    from
    > > ASP or ISAPI code, this problem actually applies to ANY server-to-server
    > > usage of XMLHttpRequest from any kind of codebase. At the most basic

    > level,
    > > there is currently no supported method for sending HTTP-based requests

    > between
    > > HTTP servers and any technique -- XMLHttpRequest or otherwise -- that is
    > > not restricted to a client machine sending the request to a server will

    > experience
    > > unforeseen problems."
    > >
    > > I'm looking into using java objects for the http communication and

    > wrapping
    > > them as COM objects.
    > >
    > > Thanks
    > > Paul.
    > >
    > >
    > > "John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > > >Tom,
    > > >
    > > >I use the xmlhttp object to get asp to talk to another server through a
    > > >proxy (hence server to server coms) ... is this what your after. I'm

    not
    > > >even sure if it handles ssl - I would guess not though.
    > > >
    > > >If not, I can tell you the code for winsock is not easy to do, the api

    is
    > > >very complicated - and from VB its a bit of a nightmare and ssl will

    add
    > > to
    > > >those complications, I have an example in VB you could have if it will

    > help
    > > >but it has no ssl support - you would need to add that.
    > > >--
    > > >Regards
    > > >
    > > >John Timney
    > > >Microsoft MVP
    > > >(http://support.microsoft.com/support/mvp/program.asp)
    > > >Co-Author Professional JSP
    > > >ISBN: 1-861003-62-5
    > > >
    > > >
    > > >
    > > >paul <pfarnan@ireland.com> wrote in message

    > news:39bf5217$1@news.devx.com...
    > > >
    > > >John,
    > > >
    > > >Thanks for the reply.
    > > >I've read Alex's article on asptoday, which was the reason I was using
    > > >XMLHTTP.
    > > >Great article and things seem simple but unfortunatley a bit more
    > > >complicated
    > > >in practice. XMLHTTP doesn't support server 2 server communication.

    Looks
    > > >like the only way is to write commands to the winsock dll directly. One
    > > >alternative
    > > >solution is a 3rd party component from serverobjects

    > (www.serverobject.com)
    > > >but this doesn't support secure communication.
    > > >
    > > >Thanks
    > > >
    > > >Paul
    > > >
    > > >
    > > >"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > > >>Paul,
    > > >>
    > > >>Sorry for the delay in replying, you might be getting a bit too deep

    in
    > > >your
    > > >>solution when easier approaches could be available. Can I suggest

    you
    > > >look
    > > >>up Alex Homer at www.asptoday.com, he has an excellent article that

    > covers
    > > >>server side xmlhttp.
    > > >>
    > > >>--
    > > >>Regards
    > > >>
    > > >>John Timney
    > > >>Microsoft MVP
    > > >>(http://support.microsoft.com/support/mvp/program.asp)
    > > >>Co-Author Professional JSP
    > > >>ISBN: 1-861003-62-5
    > > >>
    > > >>
    > > >>
    > > >>Paul <pfarnan@ireland.com> wrote in message
    > > >news:39b51215$1@news.devx.com...
    > > >>
    > > >>An update on the issue:
    > > >>I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll
    > > >>internally.
    > > >>When I built an Standard Exe test harness to test my RemSvrInt.dll and
    > > >>deployed
    > > >>it onto my NT Server box it ran OK. I was able to create an
    > > >MSXML2.XMLHTTP30
    > > >>object and call the send method posting a string to it. (It failed a

    few
    > > >>times).
    > > >>
    > > >>Afterwards, I took my RemSvrInt.dll and referenced from another

    ActiveX
    > > >DLL
    > > >>that is created by IIS. When a call was made to my RemSvrInt.dll it

    > failed
    > > >>on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object

    "~"
    > > >>failed. Being ActiveX dll they are running in the IIS server process

    > which
    > > >>it doesn't seem to like one bit.
    > > >>
    > > >>Conclusions:
    > > >>1: Server 2 Server calls work sporadically
    > > >>2: The send method of MSXML.XMLHTTP30 does not function inside of an

    IIS
    > > >>process (btw - this is on a client machine which is using PWS and

    > doesn't
    > > >>have NT Server security!)
    > > >>
    > > >>Anyone have any thoughts?
    > > >>
    > > >>Thanks
    > > >>P.
    > > >>
    > > >>"Paul" <pfarnan@ireland.com> wrote:
    > > >>>
    > > >>>John,
    > > >>>I have installed an application on my server and was calling another
    > > >server
    > > >>>and sometimes it stalled on the send (there could be other reasons)

    but
    > > >>the
    > > >>>following link explains its limitations(just in case you weren't

    > aware).
    > > >>>I haven't benchedmarked the behaviour of it yet (It does work
    > > >>sporadically).
    > > >>>
    > > >>>http://support.microsoft.com/support.../q237/9/06.asp
    > > >>>I'm using this call inside an activeX dll - apartment threaded.
    > > >>>
    > > >>>Also when you say WININET does support server to server, what do you

    > mean?
    > > >>>The following link states that the Win32 Internet functions do not

    > support
    > > >>>server implementations and should not be used from a service.
    > > >>>http://msdn.microsoft.com/workshop/n...et/wininet.asp
    > > >>>
    > > >>>As an aside. Did you have problems installing the MSXML3 on your

    > machine.
    > > >>>When I downloaded it and ran the install alongside previous version

    > .exe
    > > >>>which allows it to run with previous versions(I had msxml v1) the

    > entries
    > > >>>it placed in the registry and the progIDs seemed different. In VB

    when
    > > >I
    > > >>>had
    > > >>>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
    > > >>>When I was building a dll I replaced new with CreateObject, it failed

    > > as
    > > >>>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a
    > > >>reason/explanation
    > > >>>for this?
    > > >>>
    > > >>>I'm looking at programming sockets for the request which I was hoping

    > > to
    > > >>>avoid....(hands dirty time !)
    > > >>>
    > > >>>Thanks for your reply..
    > > >>>
    > > >>>Paul
    > > >>>
    > > >>>"John Timney (MVP)" <xyztimneyj@btinternet.com> wrote:
    > > >>>>Ive never had any problems getting the xml http object to work for

    > server
    > > >>>to
    > > >>>>server communications. You need a reference to MSXML2.XMLHTTP.3.0

    if
    > > >your
    > > >>>>using it from VB (off the cuff guess so I could have a number out) -
    > > >the
    > > >>>>object is free threaded so should be suitable for VB. Alternatively
    > > >>
    > > >>> you
    > > >>>>can use good old apartment threading with a reference to
    > > >>>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not
    > > >believe
    > > >>>>the object uses wiinet at all so you should have no problems.
    > > >>>>
    > > >>>>Although the wiinet api does supprt server to server, you can not
    > > >>>>efficiently use winnet api from vb as you seem to be aware unless

    its
    > > >a
    > > >>>vb
    > > >>>>client not a dll from asp due to threading problems with vb, if you

    > cant
    > > >>>use
    > > >>>>a third party compnent then use a socket to the remote servers port

    80
    > > >>and
    > > >>>>issue http commands direct to the port, or use java if you know the
    > > >>>>language.
    > > >>>>
    > > >>>>--
    > > >>>>Regards
    > > >>>>
    > > >>>>John Timney
    > > >>>>Microsoft MVP
    > > >>>>(http://support.microsoft.com/support/mvp/program.asp)
    > > >>>>Co-Author Professional JSP
    > > >>>>ISBN: 1-861003-62-5
    > > >>>>
    > > >>>>
    > > >>>>
    > > >>>>Paul <pfarnan@ireland.com> wrote in message
    > > >>news:39b3777a$1@news.devx.com...
    > > >>>>>
    > > >>>>> I'm trying to send a http request server to server. All I want to

    do
    > > >>is
    > > >>>>post
    > > >>>>> to an ASP page, get a response back and do some action based on

    the
    > > >>>>response...
    > > >>>>> Its looking pretty grim at the minute. I've tried 2 approaches.
    > > >>>>> 1. Using the MSXML object but this doesn't support server 2 server

    > > and
    > > >>>>hangs
    > > >>>>> on the httprequest.send( ) method
    > > >>>>> 2. The WININET API which also doesn't support server 2 server
    > > >>>>>
    > > >>>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the

    > reason
    > > >>>for
    > > >>>>> its limitations.
    > > >>>>>
    > > >>>>> I'm using VB6.
    > > >>>>>
    > > >>>>> Can anyone point me in another direction.
    > > >>>>> I need to get this done ASAP
    > > >>>>>
    > > >>>>>
    > > >>>>> Thanks
    > > >>>>> Paul
    > > >>>>>
    > > >>>>
    > > >>>>
    > > >>>
    > > >>
    > > >>
    > > >>
    > > >
    > > >
    > > >

    > >

    >
    >
    >
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center