 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / August 2004WSE 2.0 vs Remoting !?!
I'm exploring WSE 2.0 and .NET Remoting at the same time (but for different reasons!)... I read that with WSE 2.0 I can create web services to support directly a communication over TCP instead of using HTTP so it seems that now I can build a windows service to expose "web services" over TCP using WSE without IIS.... It's quite near .NET Remoting or am I wrong? Microsoft is going to the web services architectures direction with next generation products, Don Box said at PDC "are you sure it's a good solution to adopt a technology [Remoting] built by TWO developers" (for me this means: let's adopt other solutions....) and WSE 2.0 let me create something to override .NET Remoting so the questions are: a) is right to think that WSE are allowing us to avoid the use of .NET Remoting to do the same things? b) from a performance point of view (without considering the first question) which is the better solution to build a distributed intranet solution with .NET? tnx, regards pit. > It's quite near .NET Remoting or am I wrong? Its quite near, but not quite. For one, Remoting still allows you binaryFormatting as a way of transport (which is faster...) However, I believe I have read somewhere recently that tests have shown that Soap formats over the wire doesnt perform too shabbily... Remoting still allows the sharing of types and classes between 2 parties, which is why it is so .NET reliant.  SignatureThank you very much Warmest Regards, Softwaremaker Architect | Evangelist | Consultant +++++++++++++++++++++++++++++++++ > I'm exploring WSE 2.0 and .NET Remoting at the same time (but for different > reasons!)... I read that with WSE 2.0 I can create web services to support [quoted text clipped - 18 lines] > > pit. If at all possible, I recommend using WSE 2.0 to construct services that communicate over TCP. They are easier to build, and they give you a surprising amount of flexibility in exchanging custom types. The issue of "performance" may be a subjective one. How many requests will your service/remoting solution experiencing? What level of latency is acceptable? The QuickStarts that ship with WSE 2.0 make it easy to build SOAP/TCP solutions, so I would try it out and decide for yourself whether it's a good approach for what you need. There are also a number of excellent online articles, and a book by yours truly that delves into implementing SOAP/TCP services. Good luck! Jeffrey Hasan, MCSD President, Bluestone Partners, Inc. ----------------------------------------------- Author of: Expert SOA in C# Using WSE 2.0 (APress, 2004) http://www.bluestonepartners.com/soa.aspx > I'm exploring WSE 2.0 and .NET Remoting at the same time (but for different > reasons!)... I read that with WSE 2.0 I can create web services to support [quoted text clipped - 18 lines] > > pit. I would tend to agree. However if you want to play with VS 2005, wse does not install with framework 2.0 yet AFAICT. SignatureWilliam Stacey, MVP > If at all possible, I recommend using WSE 2.0 to construct services that > communicate over TCP. They are easier to build, and they give you a [quoted text clipped - 42 lines] > > > > pit. I had both .NET 1.1 and 2.* installed side-by-side. As such, I could use WSE2.0 in VS2005 with no problems....so far ;) SignatureThank you very much Warmest Regards, Softwaremaker Architect | Evangelist | Consultant +++++++++++++++++++++++++++++++++ ========================================== > I would tend to agree. However if you want to play with VS 2005, wse does > not install with framework 2.0 yet AFAICT. [quoted text clipped - 52 lines] > > > > > > pit. That is good to know. I will try installing 1.1 along side 2.0. Hope it does not chunk my beta VS 2005. Cheers! SignatureWilliam Stacey, MVP > I had both .NET 1.1 and 2.* installed side-by-side. > [quoted text clipped - 60 lines] > > > > > > > > pit. :) I hope it doesnt too. My order is slightly different. I began with .NET 1.1 first followed by .NET 2.* Good luck. ~Softwaremaker > That is good to know. I will try installing 1.1 along side 2.0. Hope it > does not chunk my beta VS 2005. Cheers! [quoted text clipped - 71 lines] > > > > > > > > > > pit. Are you using WSE 2.0 from VS 2005? How? SignatureSven > :) I hope it doesnt too. My order is slightly different. I began with .NET > 1.1 first followed by .NET 2.* [quoted text clipped - 84 lines] > > > > > > > > > > > > pit. Hi, The same way I used with VS2003 and .NET 1.1 I added the References to the Services2.dll manually and of course, updated the *.config file manually too. Since .NET 1.1 can be installed and run side-by-side with .NET 2.0, WSE assemblies can be referenced easily. The assemblies of WSE relies on a small set of the .NET Framework BCLs. Most of the work is done either internally (i.e. XML Encryption, see Microsoft.Web.Services2.Security.[Cryptography|Xml]) or via P/Invoke (i.e. Kerberos/X509, see advapi32.dll/crypt32.dll). If anything is to break, chances are that it will be the VS add-in (Microsoft WSE 2.0 Settings Tool), --> [therefore the manual settings you have to do], or one of the supported transports (i.e. TCP). hth. SignatureThank you very much Warmest Regards, Softwaremaker Architect | Evangelist | Consultant +++++++++++++++++++++++++++++++++ > Are you using WSE 2.0 from VS 2005? How? > [quoted text clipped - 95 lines] > > > > > > > > > > > > > > pit. OK, but you need to reference your assemblies in your web.config file. I am having trouble understanding how to reference my web service assembly because I don't know what its namespace or assembly name is. SignatureSven > Hi, > [quoted text clipped - 122 lines] > > > > > > > > > > > > > > > > pit. The referenced namespace for WSE2 is Microsoft.Web.Services2 These are the key configs in your *.config file for WSE2.0 <?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="microsoft.web.services2" type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration, Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </configSections> <system.web> <globalization requestEncoding="utf-8" responseEncoding="utf-8" /> <webServices> <soapExtensionTypes> <add type="Microsoft.Web.Services2.WebServicesExtension, Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="1" group="0" /> </soapExtensionTypes> </webServices> </system.web> <microsoft.web.services2> hth. SignatureThank you very much Warmest Regards, Softwaremaker Architect | Evangelist | Consultant +++++++++++++++++++++++++++++++++ > OK, but you need to reference your assemblies in your web.config file. > [quoted text clipped - 140 lines] > > > > > > > > > > > > > > > > > > pit. Yes, OK, but that's not what I meant. I want to create web services with a custom security token manager, so I need to know the namespace and assembly name of my own web service project, something that doesn't seem readily available in VS 2005 (nor is it configurable)? How do you get around that? It seems that you're the only one who gets this to work, so some guidance would be really helpful, AFAICT. SignatureSven > The referenced namespace for WSE2 is Microsoft.Web.Services2 > [quoted text clipped - 176 lines] > > > > > > > > > > > > > > > > > > > > pit.
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.