Hi guys
Just wondering why back in the CSLA 2.0 days was the BatchQueue dropped? I read somewhere rocky saying that you didn't intend to continue with it but it didn't have a reason for this. Was it because the BatchQueue had a design flaw in it or was it just something that you didn't want in the framework any more?
The reason why I ask is that I have had a need come from the business to schedule batch processes to run, etc and not that I have looked through the BatchQueue to see exactly what it does but from the sounds of it this could be very useful. Hence why I am wondering about it.
Cheers
Anthony
I think it was a question of time and space - i.e. not enough of it to fit in the next book.
The BatchQueue project was an example how to reuse the business objects to create a batch reporting solution if memory servers me correctly. It's been awhile.
Time, space, and the reality that things like PowerShell and other technologies (WF?) probably do a better job.
CSLA has become so big and complex by itself, that there was no way I could also do justice to a full batch queuing system. So it was either keep the BatchQueue and let it slowly become laughable due to lack of time to keep it up to date, or drop it and be honest.
Copyright (c) Marimer LLC