Yes, for this milestone was my idea as well. IMHO, having M1 out and to be working on a scheduler implementation is better than to be working on a scheduler implementation.
Since the name of the interface was JobEntry, the same as the class. I renamed the interface to JobEntryInterface. This can be switched back when the implementation is renewed. /Ludwig From: Thomas Vandahl [mailto:[email protected]] Sent: den 24 januari 2011 21:23 To: Turbine Developers List Subject: Re: Scheduler On 24.01.11 21:09, Ludwig Magnusson wrote: > Anyway, I believe that I have it back to the way it was before and if you > want to look at it I can commit, but if you'd rather work on a new > implementation that's fine as well. Well, I didn't want to introduce more Torque dependencies than necessary. However if we can agree that this would be for the milestone only, I am fine with your solution. A new implementation using quartz went south with my Macbook's hard disk a couple of months ago (No, no daily backups...). It was not finished anyway. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] _____ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3400 - Release Date: 01/24/11
