[sip-comm-dev] Why Sip Communicator use OSGI framework..


#1

Hi all,

Please enligten, Why sip Communicator use OSGI bundles.. ? what are
advantages using these bundles over any application..

Thanks.

···

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin


#2

Hello Muhammad

Saifuddin wrote:

Hi all,

Please enligten, Why sip Communicator use OSGI bundles.. ? what are
advantages using these bundles over any application..

Not sure what you mean by "any application" but the point of using the
OSGi architecture in general is providing modularity which makes for
better extensibility and flexibility.

In other words, with Felix and hence OSGi it is easy to customize the
application by deciding which parts you need and which you don't.

OSGi makes it easy to add features that come as new modules (bundles)
without having to necessarily modify the rest of the application. This
also makes the learning curve for new contributors less steep.
With OSGi modification of the code in one bundle is particularly
isolated from the rest of the application.

Last and certainly not least Felix and OSGi make it particularly easy to
download, install and update bundles of the application after it has
been initially deployed.

Hope this helps.

For more information you could try having a look at:
http://osgi.org
http://felix.apache.org

Cheers
Emil

···

Thanks.

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Emil,

Thanks for your reply..

would you please give me an example in code of SC where actually bundles are
stop & start..

Thanks,

···

On Sat, May 9, 2009 at 5:57 PM, Emil Ivov <emcho@sip-communicator.org>wrote:

Hello Muhammad

Saifuddin wrote:
> Hi all,
>
> Please enligten, Why sip Communicator use OSGI bundles.. ? what are
> advantages using these bundles over any application..

Not sure what you mean by "any application" but the point of using the
OSGi architecture in general is providing modularity which makes for
better extensibility and flexibility.

In other words, with Felix and hence OSGi it is easy to customize the
application by deciding which parts you need and which you don't.

OSGi makes it easy to add features that come as new modules (bundles)
without having to necessarily modify the rest of the application. This
also makes the learning curve for new contributors less steep.
With OSGi modification of the code in one bundle is particularly
isolated from the rest of the application.

Last and certainly not least Felix and OSGi make it particularly easy to
download, install and update bundles of the application after it has
been initially deployed.

Hope this helps.

For more information you could try having a look at:
http://osgi.org
http://felix.apache.org

Cheers
Emil

>
> Thanks.
>
> --
> Regards,
> Muhammad Saifuddin
>
> Blog : http://saifo.blogspot.com
> Profile : http://www.linkedin.com/in/saifuddin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin


#4

Hello Muhammad,

Saifuddin wrote:

Hi Emil,

Thanks for your reply..

would you please give me an example in code of SC where actually bundles
are stop & start..

All the Activator classes (like SipActivator, JabberActivator,
ContactlistActivator) contain a start() method which, in our current
architecture is the entry point for every bundle (until we start using
ipojo-s) .

It is up to Felix to actually call these methods and the sequence in
which it does is in lib/felix.client.run.properties

Cheers
Emil

···

Thanks,

On Sat, May 9, 2009 at 5:57 PM, Emil Ivov <emcho@sip-communicator.org > <mailto:emcho@sip-communicator.org>> wrote:

    Hello Muhammad

    Saifuddin wrote:
    > Hi all,
    >
    > Please enligten, Why sip Communicator use OSGI bundles.. ? what are
    > advantages using these bundles over any application..

    Not sure what you mean by "any application" but the point of using the
    OSGi architecture in general is providing modularity which makes for
    better extensibility and flexibility.

    In other words, with Felix and hence OSGi it is easy to customize the
    application by deciding which parts you need and which you don't.

    OSGi makes it easy to add features that come as new modules (bundles)
    without having to necessarily modify the rest of the application. This
    also makes the learning curve for new contributors less steep.
    With OSGi modification of the code in one bundle is particularly
    isolated from the rest of the application.

    Last and certainly not least Felix and OSGi make it particularly easy to
    download, install and update bundles of the application after it has
    been initially deployed.

    Hope this helps.

    For more information you could try having a look at:
    http://osgi.org
    http://felix.apache.org

    Cheers
    Emil

    >
    > Thanks.
    >
    > --
    > Regards,
    > Muhammad Saifuddin
    >
    > Blog : http://saifo.blogspot.com
    > Profile : http://www.linkedin.com/in/saifuddin

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Founder and Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Emil,

one more thing.. is from download I found three links to download the source
code of SC,
These are the following..

http://www.sip-communicator.org/index.php/Main/Download

   - Source code
snapshots<http://www.sip-communicator.org/download/nightly-builds/src>
   - All nightly builds <http://download.sip-communicator.org/nightly/>
   - Source code - sip-communicator-1.0-alpha2-src.zip
   <http://download.sip-communicator.org/alpha2/src/sip-communicator-src-1.0-alpha2.zip>(this
   source code is having different UI & only sip is working.. but other IM
   service are not)

My Question is what actually the reason to have three different source code
instead of using.. one
I confused which one should I use to enroll myself into the developement..

Thanks,

···

On Tue, May 12, 2009 at 7:28 PM, Saifuddin <saif.outwit@gmail.com> wrote:

Hi Emil,

Thanks for your reply..

would you please give me an example in code of SC where actually bundles
are stop & start..

Thanks,

On Sat, May 9, 2009 at 5:57 PM, Emil Ivov <emcho@sip-communicator.org>wrote:

Hello Muhammad

Saifuddin wrote:
> Hi all,
>
> Please enligten, Why sip Communicator use OSGI bundles.. ? what are
> advantages using these bundles over any application..

Not sure what you mean by "any application" but the point of using the
OSGi architecture in general is providing modularity which makes for
better extensibility and flexibility.

In other words, with Felix and hence OSGi it is easy to customize the
application by deciding which parts you need and which you don't.

OSGi makes it easy to add features that come as new modules (bundles)
without having to necessarily modify the rest of the application. This
also makes the learning curve for new contributors less steep.
With OSGi modification of the code in one bundle is particularly
isolated from the rest of the application.

Last and certainly not least Felix and OSGi make it particularly easy to
download, install and update bundles of the application after it has
been initially deployed.

Hope this helps.

For more information you could try having a look at:
http://osgi.org
http://felix.apache.org

Cheers
Emil

>
> Thanks.
>
> --
> Regards,
> Muhammad Saifuddin
>
> Blog : http://saifo.blogspot.com
> Profile : http://www.linkedin.com/in/saifuddin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin


#6

Hello Muhammad,

Saifuddin wrote:

Hi Emil,

one more thing.. is from download I found three links to download the
source code of SC,
These are the following..

http://www.sip-communicator.org/index.php/Main/Download

    * Source code snapshots
      <http://www.sip-communicator.org/download/nightly-builds/src>

That's the place where you get snapshots of the svn repository in case
you can't directly access it for some reason.

    * All nightly builds <http://download.sip-communicator.org/nightly/>

I don't think there's any code in here. Only a link to the above location.

    * Source code - sip-communicator-1.0-alpha2-src.zip
      <http://download.sip-communicator.org/alpha2/src/sip-communicator-src-1.0-alpha2.zip>
      (this
      source code is having different UI & only sip is working.. but
      other IM service are not)

The above contains the code for our alpha2 release. It is quite old,
which explains the different GUI (although all protocols should be
working) but it is also our last official release so we'll keep it until
we bring the new one this summer.

My Question is what actually the reason to have three different source
code instead of using.. one

I hope I've answered this. Let me know if otherwise.

I confused which one should I use to enroll myself into the developement..

If you have that option it's best to do this directly through good old SVN.

Cheers
Emil

···

Thanks,

On Tue, May 12, 2009 at 7:28 PM, Saifuddin <saif.outwit@gmail.com > <mailto:saif.outwit@gmail.com>> wrote:

    Hi Emil,

    Thanks for your reply..

    would you please give me an example in code of SC where actually
    bundles are stop & start..

    Thanks,

    On Sat, May 9, 2009 at 5:57 PM, Emil Ivov > <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>> wrote:

        Hello Muhammad

        Saifuddin wrote:
        > Hi all,
        >
        > Please enligten, Why sip Communicator use OSGI bundles.. ?
        what are
        > advantages using these bundles over any application..

        Not sure what you mean by "any application" but the point of
        using the
        OSGi architecture in general is providing modularity which makes for
        better extensibility and flexibility.

        In other words, with Felix and hence OSGi it is easy to
        customize the
        application by deciding which parts you need and which you don't.

        OSGi makes it easy to add features that come as new modules
        (bundles)
        without having to necessarily modify the rest of the
        application. This
        also makes the learning curve for new contributors less steep.
        With OSGi modification of the code in one bundle is particularly
        isolated from the rest of the application.

        Last and certainly not least Felix and OSGi make it particularly
        easy to
        download, install and update bundles of the application after it has
        been initially deployed.

        Hope this helps.

        For more information you could try having a look at:
        http://osgi.org
        http://felix.apache.org

        Cheers
        Emil

        >
        > Thanks.
        >
        > --
        > Regards,
        > Muhammad Saifuddin
        >
        > Blog : http://saifo.blogspot.com
        > Profile : http://www.linkedin.com/in/saifuddin

        ---------------------------------------------------------------------
        To unsubscribe, e-mail:
        dev-unsubscribe@sip-communicator.dev.java.net
        <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
        For additional commands, e-mail:
        dev-help@sip-communicator.dev.java.net
        <mailto:dev-help@sip-communicator.dev.java.net>

    --
    Regards,
    Muhammad Saifuddin

    Blog : http://saifo.blogspot.com
    Profile : http://www.linkedin.com/in/saifuddin

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Founder and Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Thanks Emil for the prompt reply,

Its clear now..

···

On Tue, May 12, 2009 at 7:56 PM, Emil Ivov <emcho@sip-communicator.org>wrote:

Hello Muhammad,

Saifuddin wrote:
> Hi Emil,
>
> one more thing.. is from download I found three links to download the
> source code of SC,
> These are the following..
>
> http://www.sip-communicator.org/index.php/Main/Download
>
> * Source code snapshots
> <http://www.sip-communicator.org/download/nightly-builds/src>
That's the place where you get snapshots of the svn repository in case
you can't directly access it for some reason.

> * All nightly builds <http://download.sip-communicator.org/nightly/>

I don't think there's any code in here. Only a link to the above location.

> * Source code - sip-communicator-1.0-alpha2-src.zip
> <
http://download.sip-communicator.org/alpha2/src/sip-communicator-src-1.0-alpha2.zip
>
> (this
> source code is having different UI & only sip is working.. but
> other IM service are not)

The above contains the code for our alpha2 release. It is quite old,
which explains the different GUI (although all protocols should be
working) but it is also our last official release so we'll keep it until
we bring the new one this summer.

> My Question is what actually the reason to have three different source
> code instead of using.. one

I hope I've answered this. Let me know if otherwise.

> I confused which one should I use to enroll myself into the
developement..

If you have that option it's best to do this directly through good old SVN.

Cheers
Emil
>
> Thanks,
>
>
> On Tue, May 12, 2009 at 7:28 PM, Saifuddin <saif.outwit@gmail.com > > <mailto:saif.outwit@gmail.com>> wrote:
>
> Hi Emil,
>
> Thanks for your reply..
>
> would you please give me an example in code of SC where actually
> bundles are stop & start..
>
> Thanks,
>
>
> On Sat, May 9, 2009 at 5:57 PM, Emil Ivov > > <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>> > wrote:
>
> Hello Muhammad
>
> Saifuddin wrote:
> > Hi all,
> >
> > Please enligten, Why sip Communicator use OSGI bundles.. ?
> what are
> > advantages using these bundles over any application..
>
> Not sure what you mean by "any application" but the point of
> using the
> OSGi architecture in general is providing modularity which makes
for
> better extensibility and flexibility.
>
> In other words, with Felix and hence OSGi it is easy to
> customize the
> application by deciding which parts you need and which you don't.
>
> OSGi makes it easy to add features that come as new modules
> (bundles)
> without having to necessarily modify the rest of the
> application. This
> also makes the learning curve for new contributors less steep.
> With OSGi modification of the code in one bundle is particularly
> isolated from the rest of the application.
>
> Last and certainly not least Felix and OSGi make it particularly
> easy to
> download, install and update bundles of the application after it
has
> been initially deployed.
>
> Hope this helps.
>
> For more information you could try having a look at:
> http://osgi.org
> http://felix.apache.org
>
> Cheers
> Emil
>
>
> >
> > Thanks.
> >
> > --
> > Regards,
> > Muhammad Saifuddin
> >
> > Blog : http://saifo.blogspot.com
> > Profile : http://www.linkedin.com/in/saifuddin
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@sip-communicator.dev.java.net
> <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
> For additional commands, e-mail:
> dev-help@sip-communicator.dev.java.net
> <mailto:dev-help@sip-communicator.dev.java.net>
>
>
>
>
> --
> Regards,
> Muhammad Saifuddin
>
> Blog : http://saifo.blogspot.com
> Profile : http://www.linkedin.com/in/saifuddin
>
>
>
>
> --
> Regards,
> Muhammad Saifuddin
>
> Blog : http://saifo.blogspot.com
> Profile : http://www.linkedin.com/in/saifuddin

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Founder and Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Regards,
Muhammad Saifuddin

Blog : http://saifo.blogspot.com
Profile : http://www.linkedin.com/in/saifuddin