Hi. The problem with Seasidehosting is that (I think) you have a limit of 250 MB of the HD.<br><br>Maybe a little trick is to register an account where you upload the image of a magma server. There you will have 250 MB free for that. Then you register another APP with seaside and the magma client. <br>
<br>I have no idea if 250 MB for Magma is ok or not neither your needs or your app's needs.<br><br>Netstyle offers solutions with much more space, but of course, you will have to pay. <br><br>Cheers<br><br>Mariano<br>
<br><div class="gmail_quote">On Thu, May 6, 2010 at 4:56 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<div class="im"><br>
On Wed, May 5, 2010 at 7:25 PM, Damion Mitchell <<a href="mailto:dammitchy@gmail.com">dammitchy@gmail.com</a>> wrote:<br>
> I am a newbie to Magma, and I am working on a project and I was wondering if<br>
> there is an easy way to configure my system to have Magma work on<br>
> seasidehosting. Now it is presently working on my local machine<br>
> connect<br>
> session := (MagmaSession openLocal: 'PackageDB') newSession; connectAs:<br>
> 'admin'.<br>
<br>
</div>You can connect to a Magma using a "local" connection as you have<br>
already, or via a server listening on a port. See the wiki<br>
documentation for an explaination of this.<br>
<div class="im"><br>
> I would appreciate if some assistance could be given in this regard.<br>
> Now I have implemented somewhat of a Singleton pattern, where I am allowing<br>
> one DBase Connection per user session.<br>
<br>
</div>I presume, by this, you mean, one MagmaSession for each Seaside<br>
session. Really, it is much easier to help if you will employ<br>
language consistent with Magma. "one DBase Connection per user<br>
session" requires quite a bit of effort for me to try to "guess" what<br>
you mean, since there is no "DBase" anywhere, and "user session" is<br>
ambiguous..<br>
<div class="im"><br>
> Now I am having two issues.<br>
> 1. How can I explicitly save the changes made to actual MagmaDB. As I can<br>
> store data, to the object while in memory, but if I close the image all<br>
> those changes are lost. So how can I ensure that it is also stored in the<br>
> localfile.<br>
<br>
</div>By "close the image" I presume you mean, exiting the image without<br>
saving? The image is the object memory, so if you save and exit the<br>
image, all object state are saved in the image file.<br>
<br>
If you want to commit the object state to the Magma repository, send<br>
#commit to your MagmaSession.<br>
<div class="im"><br>
> 2. I have an #unregistered method, however sometimes it works fine and<br>
> another time is complains that is doesNotUnderstand disconnect. Any hint or<br>
> solution as to why this might be happening<br>
> initialize<br>
> super initialize.<br>
> self database: PTDatabase new.<br>
> unregistered<br>
> self database session disconnect.<br>
> super unregistered.<br>
<br>
</div>No idea. It sounds like probably your "database" doesn't have a<br>
#session, and therefore your applicatoin is trying to send #disconnect<br>
to the nil (an UndefinedObject).<br>
<br>
- Chris<br>
_______________________________________________<br>
Magma mailing list<br>
<a href="mailto:Magma@lists.squeakfoundation.org">Magma@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/magma" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/magma</a><br>
</blockquote></div><br>