On Thu, May 26, 2011 at 10:38 AM, Richard S. Hall <he...@ungoverned.org>wrote:
> On 05/25/2011 09:23 PM, jie yan wrote: > >> Maybe that can be called religious flame war, but it's valuable. What we >> really need in open community is simple and perfect product in technology, >> but not many repeat manufacturing wheels like some outside companies. >> > > When implementing any software there are design trade-offs as well as > different focuses and goals. So, even though the wheel may look like a > reinvention, it is not generally the exact same wheel, only similar. While > it would be great if we could always agree on a single design and set of > trade-offs, the likelihood of that is slim. > > I agree with that. The current problem maybe that, we cannot easily see enough information about the trade-offs of each design and comparisons of them. We can also dive into the application and implementation of each solution, to find out the better one, to love and support one of them, or even to reinvent a better one based on existing design. While that's quite high cost, if there are no enough comparative information about design trade-offs that can be easily accessed. Regards, drhades -> richard > > > Regards, >> drhades >> >> -> richard >>>> >>>> Thanks >>>>> Alasdair >>>>> >>>>> >>>>> On 25 May 2011 15:29, Richard S. Hall<he...@ungoverned.org> wrote: >>>>> >>>>>> On 5/25/11 9:19, Richard S. Hall wrote: >>>>>> >>>>>>> We actually have a table in our book (OSGi in Action) that tries to >>>>>>> compare the features...perhaps I could re-create that table on a web >>>>>>> >>>>>> page... >>> >>>> Ok, I added the table to the iPOJO FAQ on wiki: >>>>>> >>>>>> >>>>>> >>>>>> >>> https://cwiki.apache.org/confluence/display/FELIX/iPOJO+FAQ#iPOJOFAQ-HowdoesiPOJOcomparetoDeclarativeServicesorBlueprint%3F >>> >>>> It's not perfect, but it is better than nothing. It should eventually >>>>>> propagate to our static pages. >>>>>> >>>>>> Clement, please double check the iPOJO features, since you've added >>>>>> >>>>> features >>> >>>> since the book has been published. >>>>>> >>>>>> -> richard >>>>>> >>>>>> On 5/25/11 5:26, jie yan wrote: >>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> Regards, >>>>>>>> drhades >>>>>>>> >>>>>>>> On Wed, May 25, 2011 at 5:11 PM, Alex Karasulu<akaras...@apache.org >>>>>>>> > >>>>>>>> wrote: >>>>>>>> >>>>>>>> On Wed, May 25, 2011 at 6:28 AM, Richard S. Hall< >>>>>>>>> >>>>>>>> he...@ungoverned.org >>> >>>> wrote: >>>>>>>>>> On 05/24/2011 09:46 PM, jie yan wrote: >>>>>>>>>> >>>>>>>>>> I wonder what is the difference between these three component >>>>>>>>>>> >>>>>>>>>> runtime. >>> >>>> They all manage service dependencies. Blueprint and iPOJO provide >>>>>>>>>> >>>>>>>>> more >>> >>>> sophisticated features than DS. Each has a different focus or goal. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I guess everyone like myself is seeing this question occur >>>>>>>>> regularly >>>>>>>>> >>>>>>>> on >>> >>>> this >>>>>>>>> mailing list. It's a valid question that perhaps we can dedicate a >>>>>>>>> wiki/web >>>>>>>>> page to with the pros and cons. >>>>>>>>> >>>>>>>>> I myself have many questions and can't really tell which is best >>>>>>>>> for >>>>>>>>> >>>>>>>> our >>> >>>> needs at directory but I do know that I have to sit down and do the >>>>>>>>> research. However our situation is much more unique since we back >>>>>>>>> configuration information needed to wire the server inside a >>>>>>>>> >>>>>>>> LDIF/LDAP >>> >>>> based >>>>>>>>> backing store. Lots to think about for us. >>>>>>>>> >>>>>>>>> Excuse the digression on our specific issues but regarding having a >>>>>>>>> >>>>>>>> page >>> >>>> dedicated to the pros and cons of each option at felix could benefit >>>>>>>>> many >>>>>>>>> of >>>>>>>>> our users. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> Alex >>>>>>>>> >>>>>>>>> >>>>>
