Re: OSGI.NET???

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John Smith (sect0r527_at_gmx.net)
Date: 07/07/04 

Date: Wed, 7 Jul 2004 14:46:52 +0200

Great to hear from you, Romu

have you/your_company actually done anything in this way? If so, please let
me know how far are you. As you correctly noticed, the service broker should
be our main focus. Regarding logging service, their is a great work of Lorne
Brinkman called .NET Logging Framework (www.theobjectguy.com/dotnetlog/), we
can use it in OSGI.NET.

Some ideas on service broker implementation. We could simply place shared
assemblies (which contain/provide services) into GAC. There are several ways
to interact with GAC (http://www.codeproject.com/dotnet/demystifygac.asp).
IMO, the most suitable for us is to use GAC API
(http://support.microsoft.com/default.aspx?scid=kb;en-us;317540).

There is also an open source implementation of OSGi R3 -
www.knopflerfish.org

Regards,
sect

Relevant Pages

  • Re: OSGI.NET???
    ... this is a totally personnal hobby task and my company is not involved in except I started from our implementation. ... For the GAC, I agree the framework should be put into, the framework services can too, but from my point the view, the bundles shouldn't. ... As you correctly noticed, the service broker should ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: OSGI.NET???
    ... Romu ... Some ideas on service broker implementation. ... to interact with GAC. ... > My company has developed its own implementation of the OSGi R3. ...
    (microsoft.public.dotnet.framework.compactframework)