Hello, Ann!

"Ann W. Harrison" wrote:

> >It depends. For example, Superserver architecture can't be used for providers,
> >at list due to security problems. But Classic is ideal for providers who lease
> >not only web but data storage too.
>
> Dmitry - and others,
>
> Could you be more specific about the security problems with superserver?
> They should go into future planning.

I'm not a security specialist, but these aspect is very clear.
Superserver holds all connection in one address space. That mean:
1. user can write UDF that can stole data from othe users.
2. user actions can crash server, so all other user connections will crush too.

I think there is nothing to do for the first. When provider place computer with
Interbase server for his customers, there must be one process per user
through web acces. By user I mean customer who stores IB database at provider's
computer. I'm not a database provider, but if I would, I'd use only Classic.
For our current WEb applications we use SuperServer, of course, and will use it
for future projects.

I don't know how difficult to support both versions of Classic and Superserver code,
but if it is not so hard, I prefer Classic to live forever :-), even if total
Classic installations will be 10% of Superserver installations.

--
Dmitry Kuzmenko, Epsylon Technologies.