Hi Jim,

> If classic becomes SMP friendly -- thread safe with a multi-threaded
> client -- is there any reason to continue differentiation of the classic
> and superserver engines? The only differences are whether the file is
> opened for shared or exclusive access and whether locks (and blocking
> ASTs) are exported. It all seems to boil down to a single engine
> option: exclusive or shared access to the physical file.

I beleive there was argument that a Cluster environment can only work on
Classic?

> The only
> significant difference is the garbage collection thread, which is a
> mistake and should be dropped anyway.

Okay, what are your ideas of implementing garbage removing in the current
architecture? Immediatly garbage collect page before storing to disk?

> If we can flush the difference between classic and superserver,
> everyone's life gets a great deal simpler.

I think everyone will agree that life (read maintenance, etc...) becomes
easier with one direction.

> What am I missing?

Time :-)

Regards,
Arno Brinkman
ABVisie

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Firebird links :
http://www.firebirdsql.com
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/


Nederlandse firebird nieuwsgroep :
news://80.126.130.81