WSE 3.0 to Indigo: What about TCP transports?

Posted by: Julia Lerman Blog - Dont Be Iffy..., on 14 Jan 2006 | View original | Bookmarked: 0 time(s)

WSE 2.0's messaging API gave us the ability to host web services outside of IIS. Though it was very cool, I didn't dig that too much because you had to give up all of the other WSE goodness that only worked in ASMX - including security. In WSE 3.0, they changed this so that you could build ASMX web services, do all of the great security stuff and then host it outside of IIS - for me this meant TCP, though there are other transports you can use as well. ...

Category: Indigo | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 3494 | Hits: 101

Similar Posts

  • WSE3 with WCF February CTP more
  • WSE: Security Token could not be retrieved vs. Permissions and some other Certificate hints more
  • TCP Tracing and WSE 3.0 - aha! Now I get it. more
  • Meet the WCF Channel Model Part 2 more
  • Why non-HTTP web services are so much cooler (for non-plumbers) with WSE 3.0 more
  • WSE3 Beta 1 Release Notes more
  • What port does WSE default to with soap.tcp://localhost? more
  • Sam Gentile on SOA and Indigo at VTdotNET more
  • Web Services Enhancements 2 SP3 Released more
  • FYI: WS-ReliableMessaging & Plumbwork Orange vNext more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD