Ann W. Harrison wrote:

>>So far I do not see any problem with the current solution as far as
>>application programmer is concerned:
>
>
> There are two problems. First is that the Vulcan engine provider does
> not include the services API. That may seem arbitrary and capricious,
> but the services code is designed to be layered on the engine, not
> embedded in it.

The second problem is that the current services can not be implemented
in Vulcan as they now exist , because

> The current implementation of the services API mixes
> layered code with internal engine calls.

I left out a sentence...

Cheers,


Ann