[jitsi-dev] What are the service characteristics from your point of view?


#1

Hi,

I am doing some analysis work on Jitsi source code since it is one
of the well know adopters of OSGi.

My question is: what are the characteristics of an object to be registered
as a service from your point of view ? Why some instances of a given class
are registered as services and other instances not ?

I wish my question was clear.

Thank you.


#2

Hi soumia,

In jitsi desktop source code, anything can be registered in OSGi, and maybe
the only requirement is its interface to be defined in
net.java.sip.communicator.service package, as all implementations can use
it.

Regards
damencho

···

On Fri, May 25, 2018 at 4:05 AM soumia soumia <soumiainf92@gmail.com> wrote:

Hi,

I am doing some analysis work on Jitsi source code since it is one
of the well know adopters of OSGi.

My question is: what are the characteristics of an object to be registered
as a service from your point of view ? Why some instances of a given class
are registered as services and other instances not ?

I wish my question was clear.

Thank you.


_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Dear Damien,

Thank you for the response.

What I wanted to know is what are your best practices to consider an
object, among several objects, as a service ?
For example, if you have two objects o1 and o2, what does it allow you to
decide that o1 is a service and o2 is not a service ?

Thank you.
Soumia.

···

On Wed, May 30, 2018 at 9:09 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi soumia,

In jitsi desktop source code, anything can be registered in OSGi, and maybe
the only requirement is its interface to be defined in
net.java.sip.communicator.service package, as all implementations can use
it.

Regards
damencho

On Fri, May 25, 2018 at 4:05 AM soumia soumia <soumiainf92@gmail.com> > wrote:

> Hi,

> I am doing some analysis work on Jitsi source code since it is one
> of the well know adopters of OSGi.

> My question is: what are the characteristics of an object to be
registered
> as a service from your point of view ? Why some instances of a given
class
> are registered as services and other instances not ?

> I wish my question was clear.

> Thank you.

> ‌
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi again,

There is no rule. Its when we need access to some service/object in
another bundle we use OSGi as a bus to register stuff so we can access
it.

Regards
damencho

···

On Thu, May 31, 2018 at 4:09 AM soumia soumia <soumiainf92@gmail.com> wrote:

Dear Damien,

Thank you for the response.

What I wanted to know is what are your best practices to consider an object, among several objects, as a service ?
For example, if you have two objects o1 and o2, what does it allow you to decide that o1 is a service and o2 is not a service ?

Thank you.
Soumia.

On Wed, May 30, 2018 at 9:09 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi soumia,

In jitsi desktop source code, anything can be registered in OSGi, and maybe
the only requirement is its interface to be defined in
net.java.sip.communicator.service package, as all implementations can use
it.

Regards
damencho

On Fri, May 25, 2018 at 4:05 AM soumia soumia <soumiainf92@gmail.com> wrote:

> Hi,

> I am doing some analysis work on Jitsi source code since it is one
> of the well know adopters of OSGi.

> My question is: what are the characteristics of an object to be registered
> as a service from your point of view ? Why some instances of a given class
> are registered as services and other instances not ?

> I wish my question was clear.

> Thank you.

> ‌
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev