Cowboy
Wed May 07 10:37:32 CDT 2008
I generally work with custom objects that are serializable and use WCF over
Remoting, as it allows you to change to a web delivery method without
reworking your code. In addition, it is simpler to code.
You can use any object that is serializable and some prefer to use DataSets,
as they are simpler to implement.
It is really up to you.
One thing to watch out for, which I have seen in many "service type"
applications is ending up with tight coupling through your objects. My last
nightmare required the exact same version of a library on both ends and the
library had been completely refactored. If it were all in house, it would
not have been as painful, of course. Service boundaries should help loosely
couple your layers, not tighten the coupling.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*************************************************
| Think outside the box!
|
*************************************************
"AAAAA" <AAAAA@hotmail.com> wrote in message
news:epfUYWFsIHA.1952@TK2MSFTNGP05.phx.gbl...
> Hi friends!
>
> What is the best architecture based in Net remoting?
> is valid get data with datareaders put this data in Generic list and pass
> it through of n tier?
> are generic list serializable?
>
> is best get data with dataset or datatable and pass it through of n tier?
> I am working with Framework 2.0. ASP.NET and C#.
>
> Thanks
>
> Regards
>
>
> Cesar
>