Re: [Fresco-devel] kit destruction not informing the server?

Stefan Seefeld <[email protected]>
Newsgroups gmane.comp.video.fresco.devel
Message-ID <[email protected]>
Nick Lewycky wrote:
> Should the server even be loading all of the kits at startup? Couldn't 
> they just be loaded on demand? Making the server store the prototype and 
> having each ServerContext clone it seems a bit unusual. You make it 
> sound as if this bug could be fixed by ensuring that the server loads 
> the PSDrawingKit on startup along with the other Kits... if that's 
> correct, it would be the best fix for the release.

but the server *does* load the PSDrawingKit on startup.
As I said, the load-on-startup is needed in order to take advantage of
the prototype pattern. How else would we be able to load the GLDrawingKit
(which is of type "Fresco::DrawingKit3D") when we ask for a
"Fresco::DrawingKit" ? Somewhere both types need to be compared, i.e. the
'is a' test needs to be performed.
Don't worry, kits are not very expensive, they don't hold a lot of state,
and I don't expect them to proliferate either, at least not in numbers that
should worry us.

> Nathaniel Smith wrote:
>  > BTW, why isn't this in the bug tracker? :-)
> 
> Because I thought we weren't supposed to file Real Bugs in it until 
> Monday. For some reason. And I can't even find the post I thought 
> supported my position. Instead I find Stefan Seefeld saying "I believe 
> the tool is getting reasonably useable to officially start using it." So 
> I guess that makes the answer to your question, "because I'm an idiot?" ;-)

no. While it *is* useable, there are all sorts of (small) bugs turning up
that I'd rather fix before we do that. But it seems we now are at a point
where we don't need to reinitialise the database any more, so we may as well
start using it.

But then don't be upset if you find a freshly installed database with no
data in it at some point. :-)
(I really hope I'll sort it all out tomorrow...)

Regards,
		Stefan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.