I'd store the job in some form of a persistent queue (msmq, ESENT, RDBMS,
filesystem, whatever), have SOMETHING (see below) process that offline, and
move to Done queue. Then have another page serve the Done stuff to the
users.
as for the offline processor - you have three main options:
1. spawn
Hello,
I am using the DictionaryAdapter to help me strongly type the
configuration settings for my application, using a technique described
here http://blog.andreloker.de/post/2008/06/Castle-DictionaryAdapter.aspx
I have a simple interface in a library called Test.Service:
ISettings {
any time I need offline processing I use a windows service with a
service bus communicating between the web and service. I favor
Rhino.ServiceBus, but I hear NServiceBus and MassTransit have the same
feature set.
On May 4, 2:07 am, Ken Egozi egoz...@gmail.com wrote:
I'd store the job in some
Something like the following also works as each config file gets fully
installed before moving to the next:
var container = new WindsorContainer(bootstrap.config)
container.Install(Configuration.FromXmlFile(facilities.config)
container.Install(Configuration.FromXmlFile(component.config)
On Apr
We are primarily using the fluent registration for all of our
components, but many times I want to be able to change a components
configuration from XML. This works fine provide the configuration is
not defined via fluent otherwise the fluent configuration replaces the
xml configuration.
A very
kurtharriger,
Have a look at this post:
http://mikehadlow.blogspot.com/2010/02/10-advanced-windsor-tricks-9.html
Cheers
John
From: kurtharriger kurtharri...@gmail.com
To: Castle Project Users castle-project-users@googlegroups.com
Sent: Wed, 5 May, 2010
I also added Active Record namespace to the project, and link to
MonoRail namespace on the main site:
http://stw.castleproject.org/
For smaller projects (Dynamic Proxy, facilities that live in their own
projects, components like validation etc) I suggest we put docs in the
root namespace.
