[Mono-list] Web Services in Mono
Kirk Marple
kirk-public@agnostic-media.com
Thu, 9 Dec 2004 14:45:57 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_009D_01C4DDFD.CE049E10
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I'd talked to Miguel once about this, and it sounds like Microsoft's Web
Services Enhancements (WSE2) aren't on the Mono roadmap, and that Indigo
would be the focal point down the road.
We have a service-oriented application that we'll be porting to Mono in the
next 6-9 months.
What are others doing for creating Web services in Mono, when they need more
than just a basic .asmx file?
Specifically I'm talking about support for WS-* standards like
WS-Addressing, WS-SecureConversation... and WS-Messaging for non-HTTP
transport.
Are people generating this stuff by hand? Or is nobody there yet with Mono?
Thanks,
Kirk
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Kirk Marple
Chief Software Architect, VP of Engineering
Agnostic Media, Inc.
e: kirk@agnostic-media.com
w: www.agnostic-media.com
You can get my Digital ID here:
<https://digitalid.verisign.com/services/client/index.html>
https://digitalid.verisign.com/services/client/index.html
------=_NextPart_000_009D_01C4DDFD.CE049E10
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.3790.218" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DTahoma size=3D2><SPAN class=3D417564122-09122004>I'd =
talked to=20
Miguel once about this, and it sounds like Microsoft's Web Services =
Enhancements=20
(WSE2) aren't on the Mono roadmap, and that Indigo would be the focal =
point down=20
the road.</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN=20
class=3D417564122-09122004></SPAN></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN class=3D417564122-09122004>We =
have a=20
service-oriented application that we'll be porting to Mono in the next =
6-9=20
months.</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN=20
class=3D417564122-09122004></SPAN></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN class=3D417564122-09122004>What =
are others=20
doing for creating Web services in Mono, when they need more than =
just a=20
basic .asmx file?</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN=20
class=3D417564122-09122004></SPAN></FONT> </DIV>
<DIV><FONT face=3DTahoma size=3D2><SPAN =
class=3D417564122-09122004>Specifically I'm=20
talking about support for WS-* standards like WS-Addressing,=20
WS-SecureConversation... and WS-Messaging for non-HTTP=20
transport.</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma size=3D2></FONT> </DIV>
<DIV><SPAN class=3D417564122-09122004><FONT face=3DTahoma size=3D2>Are =
people=20
generating this stuff by hand? Or is nobody there yet with=20
Mono?</FONT></SPAN></DIV>
<DIV><SPAN class=3D417564122-09122004><FONT face=3DTahoma=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D417564122-09122004><FONT face=3DTahoma=20
size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D417564122-09122004><FONT face=3DTahoma=20
size=3D2>Kirk</FONT></SPAN></DIV>
<DIV><SPAN class=3D417564122-09122004><FONT face=3DTahoma=20
size=3D2></FONT></SPAN> </DIV>
<DIV align=3Dleft><FONT face=3DTahoma=20
size=3D2>-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~</FONT></DIV>
<DIV align=3Dleft><FONT size=3D2><FONT face=3DTahoma>Kirk =
Marple<BR>Chief Software=20
Architect, VP of Engineering<BR>Agnostic Media, Inc.<BR>e:=20
kirk@agnostic-media.com<BR>w: <FONT=20
title=3Dhttp://www.agnostic-media.com/>www.agnostic-media.com</FONT></FON=
T></FONT></DIV>
<DIV align=3Dleft><FONT face=3DTahoma size=3D2><BR></FONT><FONT =
face=3DTahoma size=3D2>You=20
can get my Digital ID here: </FONT><A=20
href=3D"https://digitalid.verisign.com/services/client/index.html"><U><FO=
NT=20
face=3DTahoma color=3D#000000=20
size=3D2>https://digitalid.verisign.com/services/client/index.html</FONT>=
</U></A></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_009D_01C4DDFD.CE049E10--