Dmitry Yemanov wrote:

>> >
>>This already exists in SuperServer. It doesn't exist in Classic because
>>the underlying architecture does not allow a complete implementation.
>
>
> In fact, the architecture doesn't prevent it.

I still don't think you can get a complete implementation, although I
just did a quick review and it looks like approximately 99% of the
functionality ought to be available under Classic. There is no reason
why the stuff that works shouldn't be implemented.

>
>> > Also, does running a classic server create any file
>>corruption issues
>> > or other maintenance issues not normally associated with the
>> > SuperServer architecture?
>>
>>There are no problems specific to classic that we are aware of.
>
>
> AFAIK, we are. Since CS uses shared-write access to a database, there's a
> possibility to attach it via different connection strings, which may cause a
> database corruption.
>

Some testing is required to verify the true nature of the problem, but
afaik, both architectures are likely to be affected - which is why I
said 'nothing specific to classic that we are aware of'. I was just
being diplomatic, I guess.


Paul
--

Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase