SOAP/HTTP without IIS-ASP.Net

Hello,

I wonder whether with the DotNet framework 2.0, it would be possible to
write a windows application service which incorporated a server HTTTP
"embedded" (via code) without using IIS locally.

The purpose of the application is to consume SOAP messages over HTTP
containing objects (described in a blueprint XSD) and return reply
containing objects serialisé with xml (via their XSD schema)

XML-based messaging protocols have messages (requests) that travel in
both directions, this means that each end entity is both a SOAP client
and a SOAP server.
Implementations MUST be able to function as both a SOAP client and a
SOAP server

I do not want to have to install IIS and go through web services as in
the messages SAOP there would be no description of methods, but the
description of objects.

Let me know namespaces and classes.
As one example of code, or link on the web.

Thanks

Re: SOAP/HTTP without IIS-ASP.Net

You can do as much of this yourself as you want - it's just a question of
how much code you want to write.

At the "do it the hard way" end, you can write a socket listener that
listens on port 80, parses text, turns that into SOAP, then does the
relevant xsd validations. Doing this would be nuts, but it would be
possible.

WCF procivides the ability to write custom transports - there are samples
for TCP and UDP listeners. You can also write custom serializers (for
example, see the JSON serializer). I'm not sure how this would interact with
SOAP though.

At this point, you should probably poke around the documentation for WCF,
regarding custom channels, listeners, and serializers. You may be able to
get very close to what you're looking for with little code.

--
Chris Mullins

"aaa.aaa" wrote in message
news:%23EoCArzQIHA.1168@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> I wonder whether with the DotNet framework 2.0, it would be possible to
> write a windows application service which incorporated a server HTTTP
> "embedded" (via code) without using IIS locally.
>
> The purpose of the application is to consume SOAP messages over HTTP
> containing objects (described in a blueprint XSD) and return reply
> containing objects serialisé with xml (via their XSD schema)
>
> XML-based messaging protocols have messages (requests) that travel in both
> directions, this means that each end entity is both a SOAP client and a
> SOAP server.
> Implementations MUST be able to function as both a SOAP client and a SOAP
> server
>
> I do not want to have to install IIS and go through web services as in the
> messages SAOP there would be no description of methods, but the
> description of objects.
>
> Let me know namespaces and classes.
> As one example of code, or link on the web.
>
> Thanks

Re: SOAP/HTTP without IIS-ASP.Net

Thanks for your comment.

What will be from your point of view the best way to do it ?

With IIS & ASP.NET & DotNEt 3.X ?
instead of own solution ?

Can you develop your point of view ?

Thanks




Chris Mullins [MVP - C#] a écrit :
> You can do as much of this yourself as you want - it's just a question of
> how much code you want to write.
>
> At the "do it the hard way" end, you can write a socket listener that
> listens on port 80, parses text, turns that into SOAP, then does the
> relevant xsd validations. Doing this would be nuts, but it would be
> possible.
>
> WCF procivides the ability to write custom transports - there are samples
> for TCP and UDP listeners. You can also write custom serializers (for
> example, see the JSON serializer). I'm not sure how this would interact with
> SOAP though.
>
> At this point, you should probably poke around the documentation for WCF,
> regarding custom channels, listeners, and serializers. You may be able to
> get very close to what you're looking for with little code.
>
> --
> Chris Mullins
>
> "aaa.aaa" wrote in message
> news:%23EoCArzQIHA.1168@TK2MSFTNGP02.phx.gbl...
>> Hello,
>>
>> I wonder whether with the DotNet framework 2.0, it would be possible to
>> write a windows application service which incorporated a server HTTTP
>> "embedded" (via code) without using IIS locally.
>>
>> The purpose of the application is to consume SOAP messages over HTTP
>> containing objects (described in a blueprint XSD) and return reply
>> containing objects serialisé with xml (via their XSD schema)
>>
>> XML-based messaging protocols have messages (requests) that travel in both
>> directions, this means that each end entity is both a SOAP client and a
>> SOAP server.
>> Implementations MUST be able to function as both a SOAP client and a SOAP
>> server
>>
>> I do not want to have to install IIS and go through web services as in the
>> messages SAOP there would be no description of methods, but the
>> description of objects.
>>
>> Let me know namespaces and classes.
>> As one example of code, or link on the web.
>>
>> Thanks
>
>

Re: SOAP/HTTP without IIS-ASP.Net

Thanks for your comment.

What will be from your point of view the best way to do it ?
With IIS & ASP.NET & DotNEt 3.X ?
instead of own solution ?

Can you develop your point of view ?

To complement :

The Implementers are REQUIRED to use this stack protocol :

Messaging uses XML
SOAP
HTTP
SSL
TCP
IP
Ethernet

All the schema (xsd) will be provided by an administration.

XML-based messaging protocols have messages (requests) that travel in
both directions, this means that each end entity is both a SOAP
client and a SOAP server.
Implementations MUST be able to function as both a SOAP client and a
SOAP server


>
>
> Chris Mullins [MVP - C#] a écrit :
>> You can do as much of this yourself as you want - it's just a question
>> of how much code you want to write.
>>
>> At the "do it the hard way" end, you can write a socket listener that
>> listens on port 80, parses text, turns that into SOAP, then does the
>> relevant xsd validations. Doing this would be nuts, but it would be
>> possible.
>>
>> WCF procivides the ability to write custom transports - there are
>> samples for TCP and UDP listeners. You can also write custom
>> serializers (for example, see the JSON serializer). I'm not sure how
>> this would interact with SOAP though.
>>
>> At this point, you should probably poke around the documentation for
>> WCF, regarding custom channels, listeners, and serializers. You may be
>> able to get very close to what you're looking for with little code.
>>
>> --
>> Chris Mullins
>>
>> "aaa.aaa" wrote in message
>> news:%23EoCArzQIHA.1168@TK2MSFTNGP02.phx.gbl...
>>> Hello,
>>>
>>> I wonder whether with the DotNet framework 2.0, it would be possible
>>> to write a windows application service which incorporated a server
>>> HTTTP "embedded" (via code) without using IIS locally.
>>>
>>> The purpose of the application is to consume SOAP messages over HTTP
>>> containing objects (described in a blueprint XSD) and return reply
>>> containing objects serialisé with xml (via their XSD schema)
>>>
>>> XML-based messaging protocols have messages (requests) that travel in
>>> both directions, this means that each end entity is both a SOAP
>>> client and a SOAP server.
>>> Implementations MUST be able to function as both a SOAP client and a
>>> SOAP server
>>>
>>> I do not want to have to install IIS and go through web services as
>>> in the messages SAOP there would be no description of methods, but
>>> the description of objects.
>>>
>>> Let me know namespaces and classes.
>>> As one example of code, or link on the web.
>>>
>>> Thanks
>>
>>

Re: SOAP/HTTP without IIS-ASP.Net

Hi,

Your choice would be to use WCF with the following options:
- basicHttpBinding (ASP.Net WebServices compliant)
- transport mode security (HTTPS, requires a server certificate)
- the rest of your requirements will be fullfilled as well

Although, I would discuss netTcpBinding with administrators as it uses much
more efficient serialization and offers much better network performance
(when we are talking about the amount of the data sent over the wire,
negotiating security, etc.).

The main question is _WHY_ HTTP, SOAP and XML are required?

A bit more of basic information you can find here:
http://msdn2.microsoft.com/en-us/library/ms730879.aspx

--
Best regards,
Cezary Nolewajka

Consultant | Microsoft Services | Microsoft | Poland

"aaa.aaa" wrote in message
news:e7Hpgr6QIHA.5524@TK2MSFTNGP05.phx.gbl...
> Thanks for your comment.
>
> What will be from your point of view the best way to do it ?
> With IIS & ASP.NET & DotNEt 3.X ?
> instead of own solution ?
>
> Can you develop your point of view ?
>
> To complement :
>
> The Implementers are REQUIRED to use this stack protocol :
>
> Messaging uses XML
> SOAP
> HTTP
> SSL
> TCP
> IP
> Ethernet
>
> All the schema (xsd) will be provided by an administration.
>
> XML-based messaging protocols have messages (requests) that travel in
> both directions, this means that each end entity is both a SOAP
> client and a SOAP server.
> Implementations MUST be able to function as both a SOAP client and a
> SOAP server
>
>
>>
>>
>> Chris Mullins [MVP - C#] a écrit :
>>> You can do as much of this yourself as you want - it's just a question
>>> of how much code you want to write.
>>>
>>> At the "do it the hard way" end, you can write a socket listener that
>>> listens on port 80, parses text, turns that into SOAP, then does the
>>> relevant xsd validations. Doing this would be nuts, but it would be
>>> possible.
>>>
>>> WCF procivides the ability to write custom transports - there are
>>> samples for TCP and UDP listeners. You can also write custom serializers
>>> (for example, see the JSON serializer). I'm not sure how this would
>>> interact with SOAP though.
>>>
>>> At this point, you should probably poke around the documentation for
>>> WCF, regarding custom channels, listeners, and serializers. You may be
>>> able to get very close to what you're looking for with little code.
>>>
>>> --
>>> Chris Mullins
>>>
>>> "aaa.aaa" wrote in message
>>> news:%23EoCArzQIHA.1168@TK2MSFTNGP02.phx.gbl...
>>>> Hello,
>>>>
>>>> I wonder whether with the DotNet framework 2.0, it would be possible to
>>>> write a windows application service which incorporated a server HTTTP
>>>> "embedded" (via code) without using IIS locally.
>>>>
>>>> The purpose of the application is to consume SOAP messages over HTTP
>>>> containing objects (described in a blueprint XSD) and return reply
>>>> containing objects serialisé with xml (via their XSD schema)
>>>>
>>>> XML-based messaging protocols have messages (requests) that travel in
>>>> both directions, this means that each end entity is both a SOAP client
>>>> and a SOAP server.
>>>> Implementations MUST be able to function as both a SOAP client and a
>>>> SOAP server
>>>>
>>>> I do not want to have to install IIS and go through web services as in
>>>> the messages SAOP there would be no description of methods, but the
>>>> description of objects.
>>>>
>>>> Let me know namespaces and classes.
>>>> As one example of code, or link on the web.
>>>>
>>>> Thanks
>>>
>>>

Re: SOAP/HTTP without IIS-ASP.Net

of God we have not come to that. Woe to
these priests! But we hope that God will bestow His mercy upon us that we
shall not be of them.

Saint Peter, Epistle ii: false prophets in the past, the image of future
ones.

889.... So that if it is true, on the one hand, that some lax monks and some
corrupt casuists, who are not members of the hierarchy, are steeped in these
corruptions, it is, on the other hand, certain that the true pastors of the
Church, who are the true guardians of the Divine Word, have preserved it
unchangeably against the efforts of those who have attempted to destroy it.

And thus true believers have no pretext to follow that laxity, which is only
offered to them by the strange hands of these casuists, instead of the sound
doctrine which is presented to them by the fatherly hands of their own
pastors. And the ungodly and heretics have no ground for publishing these
abuses as evidence of imperfection in the providence of God over His Church;
since, the Church consisting properly in the body of the hierarchy, we are
so far from being able to conclude from the present state of matters that
God has abandoned her to corruption, that it has never been more apparent
than at the present time that God visibly protects her from corruption.

For if some of these men, who, by an extraordinary vocation, have made
profession of withdrawing from the world and adopting the monks' dress, in
order to live in a more perfect state than ordinary Christians, have fallen
into excesses which horrify ordinary Christians, and have become to us what
the false prophets were among the Jews; this is a private and personal
misfortune, which must indeed be deplored, but from which nothing can be
inferred against the care which God takes of His Church; since all these
things are so clearly foretold, and it has been so long since announced that
these temptations would arise from people of this kind; so that when we are
well instructed, we see in this rather evidence of the care of