Ken Kolda
10/26/2004 8:32:00 PM
Generally I'd say that questions that are very specific and have specific
answers will get the fastest response. Architecture questions such as the
one you asked requires a lot more to get a useful response. In particular,
it's hard when the system has a number of moving parts and you're asked to
make a judgement of what's a "good" implementation when you know you don't
have 100% knowledge of the system or requirements.
Now, in response to your original post, having the UI interact with the
Windows Service for all data definitely has its advantages. It completely
encapsulates the data access logic in your service, so you can choose what
to optimize through caching, how best to lock data, etc.
The disadvantage, as you noted, is the decreased performance of passing data
across the wire twice. I think the answer will depend on how
performance-contrained your system is. If performance is a top concern, I'd
say go to SQL directly unless the service has the data in a format/cache
that makes it especially accessible/searchable/etc. I'd say it's a safe
assumption that unless your service provides a significant performance boost
in some manner, using SQL directly will give the best results.
Ken
"Mark Oueis" <markoueis@hotmail.com> wrote in message
news:b1800bd3.0410261208.5e34e21e@posting.google.com...
> When something like this doesn't get answered, is it because:
>
> 1) Nobody has the time
> 2) It takes time before someone realizes its there
> 3) Nobody cares enough to answer it
> 4) It got "mis-posted" some how
>
> Sometimes my posts get answered within a few hours, and another times
> they NEVER get answered. What's the usual criteria so that i can "post
> better"?
>
> Mark