Hi people, My code is also suffering. I would vote for adding the second generic parameter.
"then everbody has to create an iterator with 2 and 90+% of the cases it" 10% is a lot... By the way... the generification of IDataProvider... was it the one person decision or it was discussed somehow? Vitaly On Wed, Apr 23, 2008 at 11:26 AM, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > > Jan Kriesten wrote: > > > > > Hi Johan, > > > > > > > But how do you cache those objects? > > > Are those cached over all request so pretty much readonly ? > > > > > > > yes, they are. > > > > caching (and also marking as dirty) of objects is encapsulated within the > dao - > > so i do not have to worry much about this. > > > > also, IDataProvider isn't supposed to work only for Databases, right? > suppose > > the following (which i actually also have): i get a list of rssfeed-urls > from > > the database and within model i retrieve them - that's called 'separation > of > > concerns' which is also good programming style. > > > > I'd still say that's a data provider which provides rss feeds not rss feed > URLs. The fact that you want to retrieve them lazily seems an implementation > detail to me, not something which should go in the interface of > IDataProvider. > > Regards, > Sebastiaan > > > > best regards, --- jan. > > > > >
