241 reputation
16
bio website
location Brisbane, Australia
age 35
visits member for 3 years, 2 months
seen Oct 1 at 23:27

Oct
15
comment Should we create classes just to group properties
Thanks for your answer Frank. I have added to my question to give a bit more information. With that in mind, would your thoughts still be the same? Cheers.
Oct
14
revised Should we create classes just to group properties
Added more detail
Oct
14
revised Should we create classes just to group properties
Added more detail
Oct
14
asked Should we create classes just to group properties
Aug
5
awarded  Popular Question
Oct
20
awarded  Yearling
Sep
2
accepted Distributed Transaction Framework across webservices
Aug
30
asked Distributed Transaction Framework across webservices
Aug
14
accepted Is it OK for a function to modify a parameter
Aug
14
comment Is it OK for a function to modify a parameter
All these answers pretty much sum up our own discussions. This seems to be a question with no real answer. Your statement "Yes, you're returning the same object as you passed in, but it makes the API clearer." pretty much answered our question.
Aug
13
awarded  Nice Question
Aug
13
asked Is it OK for a function to modify a parameter
Jul
30
accepted Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
Jul
30
comment Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
That was a great link. I like way he describes simple vs easy. I'm still finding my feet when it comes to implementing OO principles, so when I get comments like "it's over engineered", I find it hard to defend against. I just know/feel its better than what I was doing. All these answers and that link just reinforced that I'm heading in the right direction. Many thanks for your answer.
Jul
30
comment Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
It's actually a far simpler scenario. The website only talks to one site service at any one time. There is a site switcher module that allows the user to change which site service the mediator uses, but the rest of application has no idea it has been switched. In truth, the mediator doesn't even know that it's using wcf. It just has a reference to an object it passes calls onto. that object can be swapped out at any time. Wcf being very easy to implement and create proxies at runtime, means I just need to store a list of uri's on the central server that I can add to or remove as needed.
Jul
30
revised Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
fixed spelling
Jul
28
awarded  Editor
Jul
28
revised Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
fixed some grammar
Jul
27
asked Is my mediator layer a sensible way to manage this scenario using the Single Responsibility Principle?
Oct
23
awarded  Scholar