On 10/9/13 11:23 , CLEMENT Jean-Philippe wrote:
I guess this is not the issue. From my understanding, Aries in itself is already too 
heavy for him and he would like the "Subsystems specification and Common Namespaces 
Specification" implementation alone.

Ah. I would have assumed that the implementation from Aries would be usable independently from anything else in Aries...if not, then I see.

-> richard


Don't know if it makes sense...

JP

-----Message d'origine-----
De : Richard S. Hall [mailto:[email protected]]
Envoyé : mercredi 9 octobre 2013 14:32
À : [email protected]
Objet : Re: Apache Felix and OSGI R5

On 10/9/13 08:07 , Roland wrote:
Hi,
thanks for your reply. I am asking because I do not want to obtain
additional overhead by the integration of Apache Aries (concerning the
starttime). I need a very lightweight implemention.
What makes you think an implementation at Felix would be any lighter weight?

This is not something integrated into the framework, it is an externally 
implemented piece of functionality. Just like any bundle. The weight of the 
implementation is purely dependent on implementation choices and not in which 
project it originated.

-> richard

Regards
Roland



--
View this message in context:
http://apache-felix.18485.x6.nabble.com/Apache-Felix-and-OSGI-R5-tp500
4939p5005462.html Sent from the Apache Felix - Users mailing list
archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to