[osg-submissions] DatabasePager : User can easy modify database threading behave....

[Robert Osfield]

Hi Adrian,

I plan to add methods to provide public controls of thread setup
within DatabasePager, but not quite what you've implemented.  The
problem with the enum approach you've taken is that one is limited the
the number of combinations of threads you can set up.  While your
changes do offer more control than no controls that we have present,
I'm going to hold back from merging as I believe there is a more
flexible API  is required.

W.r.t the DatabaseThreadCallback, this seems a very problem specific
solution.  Another route might be to subclass the DatabaseThread
object yourself, this would allow you to store your own custom data as
well as the entry/exit of the run method.  This would however, require
one to register a create DatabaseThread callback... or a have
setDatabaseThread interface.

To refine what API would be required could you explain what you are
trying to do that is different to what the standard DatabasePager
requires?

Robert.

On Fri, Jun 6, 2008 at 2:24 PM, Adrian Egli OpenSceneGraph (3D)
<3dhelp at gmail.com> wrote:
> hi robert,
>
> i can not use the default database pager of openscenegraph for my
> application, in need a method to configure the database pager. for one
> application we need only request of http type or other only non http request
> should be handled. and for the most. i don't know wether it make sense or
> not, but the user can also more easy test the latest threading progresss you
> implement in the database pager core. so we can configure with a static
> template configure how the database pager should set up
> the database paging threads.
>
> then a added a starting callback (database pager thread : first line entered
> the run method, ... , and before finish / exit from run method a second
> callback method.) i need this because i have to register and unregister all
> running threads against
> an application instance. is to hard to explaine why i have to use this, but
> i need, this is more easy to solve such an problem. as we can not overload
> the database threading object, this would be the easiest solution for such a
> problem.
>
> regards adrian
>
>
> --
> ********************************************
> Adrian Egli
> _______________________________________________
> osg-submissions mailing list
> osg-submissions at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
>
>