Assuming you don't want to download managed code to your client, the easiest way to do this is with the DHTML behavior for web services; you can find that on MSDN somewhere.
If that doesn't work for you, it's certainly possible to build a web service client in javascript, using XmlHttp for communications...not trivial, but not all that difficult either. Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com http://www.rassoc.com/gregr/weblog/ -----Original Message----- From: The DOTNET list will be retired 7/1/02 [mailto:[EMAIL PROTECTED]] On Behalf Of Steven Fraser Sent: Thursday, June 27, 2002 3:33 AM To: [EMAIL PROTECTED] Subject: Re: Server side controls vs client side script. Hi Mattias, How do you go about using IE as a direct client to a WebService? Regards, Steven Fraser The views expressed here are mine and not those of my employer -----Original Message----- From: Matthias Hertel [mailto:[EMAIL PROTECTED]] Sent: 27 June 2002 07:22 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Server side controls vs client side script. This argumention is right and false - it depends on the way you implement your pages and is not .NET specific. Sample: You have a HTML Form with 20 kByte that uses Data of 1 kByte that is displayed and modified in 4 fields. Case 1: If you implement a server-site validation on every onchange-event the data is uploaded 4 times to the server for validation and 4 times the whole Page with data comes back to the client. The final submit only tranfers the data. Sum: ~ 21 + 4*(1+21) + 1 = 110 kbyte (if no errors in input) Case 2: You implement a server-site validation when the form is submitted there is no up/download while the values in the fields are changed. Sum: ~ 21 + 1 = 22 kbyte (if no errors in input) Case 3: Same as Case 2 but you ADD a client-site validation. You only have to add some HTML+JScript code that's transfered to the client. Sum: ~ 21 + 1 + 2 = 24 kbyte (even if some errors while editing input) Case 4: Server-site validation is done by calling a WebService. It is possible to use the IE as a direct client to a webservice and this enables a full featured validation including reference data-lookup. Sum: ~ 21 + 1 + 4*1 + 2 = 28 kbyte (even if some errors while editing input) Discuss: All of these cases can be implemented on every server-plattform (.NET, ASP, JSP, PHP,...) so this is not .NET specific. Some people use every new feature they can get; they should think about a <asp:label runat:server ...>. Programming the Case 1 is also done in some of the .NET Samples but showing the possibilities doesn't mean that you have to us them. Mixing HTML and ASP.NET objects also makes sense. Case 4 is not suppored very well by the existing ASP.NET classes but calling webservices directly from the client enables a lot of features. We implement our solution this way. ----- Ursprüngliche Nachricht ----- Von: "Steve Miller" <[EMAIL PROTECTED]> Ges.: 26.06.02 16:50:35 An: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Betreff: [DOTNET] Server side controls vs client side script. Some client-side code purist argue that ASP.NET's server side controls put to much of a load on the server and cause to many round trips to the server. When you are pitching ASP.NET and run into these arguments how do you answer these criticisms of ASP.NET? Steve Miller You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. ______________________________________________________________ CONFIDENTIALITY NOTICE This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you are not the intended recipient, please contact us immediately. The contents of any attachments in this e-mail may contain software viruses, which could damage your own computer system. While Marlborough Stirling has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checking procedure before opening any attachment. Marlborough Stirling plc, Registered No. 3008820, Allen Jones House, Jessop Avenue, Cheltenham, Gloucestershire, GL50 3SH Tel: 01242 547000 Fax: 01242 547100 http://www.marlborough-stirling.com The following companies are subsidiaries of Marlborough Stirling plc and are registered in England and Wales at the above address: Marlborough Stirling PLC, Registered No. 3008820 The Marlborough Stirling Group PLC, Registered No. 1855353 Marlborough Stirling Administration Limited, Registered No. 2341195 Metgem Limited, Registered No. 02341195 You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
