FUTURE POSTS
- RavenDB on AWS Marketplace - about one day from now
- Production postmortem: The race condition in the interlock - 5 days from now
- When racing the Heisenbug, code quality goes out the Windows - 7 days from now
- Pricing transparency in RavenDB Cloud - 9 days from now
- Who can cancel Carmen Sandiego? - 12 days from now
There are posts all the way to Apr 14, 2025
Comments
about your nomenclature: which classes do you call XxxxImpl ?
@bobfox,
Usually, very few.
But I wanted to make a clearer separation of the service and implementation
Isn't this awfully... Heavy?
Peter,
That is for a talk that I am going to give tomorrow. It is showing an aspect of how to build a real application.
Ayende would you put the talk presentation online. I have recently been thinking about best to develop applicatings using Castle and Monorail. Most examples use the model as a data access layer but the problems I have with this is that if you want to introduce services things get tricky. This example would really help.
I know the way around this is to introduce the repository pattern but I haven't investigated this thoroughly.
I would like to, but it is going to be in Hebrew, and I don't know if I will be able to have a mic to the computer there.
That scuppers that plan. Maybe you could put the example up for download when you are done with it? IT would be nice to see how you go about unit testing it etc.
Kind of pattern happy there are we ayende ;)
And I didn't even started posting about my new ProxyDecoratingMomentoStrategyImpl !
Yeah, it is something for a presentation, so show it important.
Funny, I was just writing a Visitor for one of those!
/Mats
As for offering services based on a model: What about creating a Service Layer that both the external service and the application use?
Comment preview