roger. On Mon, Sep 29, 2008 at 1:46 PM, Ayende Rahien <[EMAIL PROTECTED]> wrote:
> Okay, that make sense. > I am now going through the source code and comparing hib to nh. > In particular, me and Fabio would like to make an alpha 1 release, but I > would like to have a solid understanding on the difference that we have > between the two. > > If you can watch the commit stream for today and tomorrow, and comment on > what you think, I would be grateful. > > > On Mon, Sep 29, 2008 at 8:39 PM, Kailuo Wang <[EMAIL PROTECTED]>wrote: > >> When I ported that part, there is no WorkType.COLLECTION yet, so basically >> I let that Layer class do nothing. >> Once we have WorkType.COLLECTION, we just need to un-comment the line >> return type != WorkType.COLLECTION ; >> and return type == WorkType.COLLECTION; >> >> >> On Mon, Sep 29, 2008 at 12:03 PM, Ayende Rahien <[EMAIL PROTECTED]>wrote: >> >>> What is the deal with BatchedQueueingProcessor.Layer ? >>> It looks like it is supposed to process collection on second go, but it >>> always process everything in the first go, and nothing in the second. >>> >>> >>> LuceneWork and derivatives looks like a classic textbook DON'T DO THIS >>> example for how not to use inheritance. I am leaning toward making the >>> behavior use polymorphism rather than explicit checks everywhere. >>> >>> >>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
