Embedded Magma database

[Chris Muller]

After more thinking, there is a (fairly common!) scenario where
developers will not feel the need to wrap the MagmaServerConsole in
their own application-server wrapper.  In other words, just a plain
vanilla Magma server image.

In these cases, a Magma server image is simply saved and exited while
its running, and this can even be performed remotely ("mySession
serverSaveAndExit").

Under this case, when the server image is restarted, only Magma's own
startUp: code re-establishes the files and sockets, your application
code will not have the opportunity to handle any warnings if there are
any.

I will fix that..

 - Chris


On Fri, Sep 12, 2008 at 7:12 PM, Chris Muller <asqueaker at gmail.com> wrote:
> Hi Jerry, yes Magma may signal warnings which you will need to handle
> if you want to run headless.  Are you familiar with handling
> exceptions in Squeak?  Here is the pattern:
>
>  [ ..do some squeak code.. ]
>    on: Warning
>    do:
>        [ : warning |
>        ..log the warning somewhere if you want...
>        warning resume ]
>
> Honestly, I'm curious why you would be receiving that particular warning..
>
>
>
> On Fri, Sep 12, 2008 at 4:15 PM, Jerry Bell <jdbell at oxfordmetamedia.com> wrote:
>> Hi,
>>
>> I'm building a simple web application with an embedded Magma database which
>> will run on a headless Linux appliance.
>>
>> A few times while developing the system, I've had a dialog window when
>> starting Squeak which has asked me to OK a recovery of the Magma database.
>>
>> Obviously I won't have a UI on this headless appliance.  What do I need to
>> do to make sure all of those types of interaction are handled by my
>> application?
>>
>> Thanks,
>>
>> Jerry
>>
>>
>> _______________________________________________
>> Magma mailing list
>> Magma at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/magma
>>
>