Hi guys,
ok, back to the roots now.
On Fri, 2006-08-18 at 08:07 -0500, Allen Bierbaum wrote:
>
> I don't think I clearly said why we were thinking about this. I know I
> could do this in my applications, but I wanted to see if there was
> interest in having OpenSG use it for it's own libraries.
There is no real reason why it couldn't.
> As part of OpenSG 2.0, it looks like there has been an effort to break
> things up into smaller libraries. This good because it makes the
> compile time faster and makes things a little more modular. But it also
> means that applications need to know all the libraries they need to link
> against. So the idea was, would it be possible to make it so users just
> link against some core library and then that core takes care of going
> out and loading all the "plugins" or "extension" it can. And then treat
> as much of the current node cores, etc as extensions to the core. (ie.
> load them up dynamically). This would hopefully make things easier for
> the user and really start pushing OpenSG's strengths of extensibility
> and a stable API.
As discussed later in this thread, not without giving up link checks.
> Additionally, OpenSG currently has all of it's image loaders and file
> loaders compiled into the System library IIRC. It would be nice to make
> all those loaders separate libraries that are dynamically loaded as
> needed. AFAIK, all the support is there, it has just never been done.
That should be much easier, as the image loading goes through the
manager that can dynamically search for the lib to load the extension
image. Same thing for file loaders, all of these can be linked
explicitly at runtime.
> Is that more clear?
Yup, but I don't see a solution for the general case. :(
I'm not sure hoe much of a problem it is really going to be. We could
create some meta-libs that contain nothing themselves but just link
against some standard libraries to virtually merge some of the libs
together into something that resembles our current system lib without
the disadvantages. For things that depend on other libs that automatism
won't work, as they need to be present. Given that there won't be too
many things like that, I'd think that it would be acceptable for the
user to use the reflective interface for creation of those, and have the
FCFactory try to dynamically load them at runtime and return NullFC if
it fails, or, if the app really depends on them, they just have to be
there and can be linked like everything else.
Not a great solution, but I don't see a better way.
Comments welcome
Dirk
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
