I think what you are talking about is an "application server". Magma is just a database server. However, in this case, you should look at the change set "ClientServerSupport". In here you will find MaRequestServerForTcp and MaRemoteServerLink. Magma uses these to pass its objectified requests across the network. But you can define your own set of "request" classes for your web app, and implement a class to be your "request processor" (look at references to the variable "requestProcessor" in MaRequestServer to see the three or so methods you would need to implement. One of them I know is #protocol, the collection of classes that are your requests and responses).

In your request processor, you would simply establish a local connection to the Magma database. Keeping track of YOUR clients would be your responsibility, because as far as Magma is concerned, it would only have ONE client: Your web-app server.

I hope this helps..

--- Avi Bryant avi@beta4.com wrote:

Chris,

Another quick question -

Magma seems to be intended to be run either client/server with a number of clients, or single-image with a lone connection. The configuration I'm interested in, however, is large numbers of clients all in the same image (and thus, ideally, without a separate server image). I imagine others doing web apps will want the same. How hard would it be to support this?

Thanks, Avi

__________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com