Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Where to start
Message
 
À
12/02/2004 00:03:24
Information générale
Forum:
ASP.NET
Catégorie:
The Mere Mortals .NET Framework
Titre:
Divers
Thread ID:
00876130
Message ID:
00876893
Vues:
9
>Larry,
>
>I don't use the MM framework, but I wanted to add one thing to what you've said here. You're definitely going about it the right way by calling a WebService on the front end to get/save your data, but I'd also take it one step further and serialize your DataSet to XML and pass XML back and forth to/from the WebService. Passing a DataSet back and forth *does* work, but keep in mind if you do it that way that the WebService will probably not work for other applications that are not .NET apps. If you're 100% sure that nothing but a .NET app will access your WebService, then it doesn't matter if you're passing DataSets. Still, nothing's ever 100% ... use XML instead. =)

While I agree with this to some extent, remember that you can always get into the Web Service anyway. For example with the SOAP toolkit you can drill into the XML document and peel out the DataSet XML. So you can always get at it.

THe problem is that there's no standard way of passing XML across the wire. Strings work for everybody, but they also bloat because if you return XML as a string it gets encoded. If you pass a DOMNode back most clients won't understand that either so you're back to the same scenario as a DataSet.


I've modified my thinking a bit based on this and feel that if your primary target is .Net it sure is nice to be able to pass a dataset back and consume it without further work.


BTW, Come to think of it - digging into SOAP XML from a .Net Web Service is actually much harder than most other tools unless you use raw SOAP client access... Luckily I've never had to do that yet <g>...






>
>~~Bonnie
>
>
>
>>Thanks Kevin thats clears up some of my misunderstanding of the business object. So if I get this you can have a webservice that returns the DataSet from the business object. Then call the webservice on the front end get the ds assign it to a new business object and make changes to the ds. Then get the ds.GetChanges() which passes a ds containing just the changes. Pass the ds with the changes to a webservice that creates a business object and call the SaveDataSet and pass it the ds with the changes in it. Am I totaly in outer space here or does this sound like it will work ?
>>
>>Thanks
>>
>>Larry G Hawke
+++ Rick ---

West Wind Technologies
Maui, Hawaii

west-wind.com/
West Wind Message Board
Rick's Web Log
Markdown Monster
---
Making waves on the Web

Where do you want to surf today?
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform