Starting Seaside block the develpment environment

Hi,

Why starting Seaside block my development environment ?

I'm using Jade but the same happens with Topaz.

If i evaluate in a workspace:
WAGsSwazooAdaptor startOn: 8888.

My development environment hangs. If i close the "Hard Break - SoftBreak" window the i can use the DE again.

[WAGsSwazooAdaptor startOn: 8888.] forkAt: xx. Does not work either.

The following links have usefull information but after read it i can not run Seaside without blocking the Jade environment. The same with Topaz i can run Seaside from topaz after that i can not use Topaz anymore. Ctrl + C free topaz but shutdown seaside.

Which is the best way to run Seaside without blocking the develpment environment ?

https://code.google.com/p/glassdb/wiki/ControllingSeaside30Gems
http://forum.world.st/Starting-Swazoo-from-GemTools-td3649293.html#a3650200
http://gemstonesoup.wordpress.com/2009/04/15/glass-beta-update-working-with-soap-preview/#GsProcesses

Regards,
Bruno

Hi Bruno,

You are experiencing a limitation of GemStone’s interaction process. Specifically, code only runs in GemStone when the client has sent a command to the server and is waiting for a response. Once a response is received, then control is back on the client. Think of it as a ping-pong ball that is passing back and forth across a net between two players. The ball is either on the client or on the server, and to do something you have to have the ball.

This is different from the typical client Smalltalk environment (e.g., Pharo) where you can fork a process and it keeps running while your UI is still active.

In GemStone the right thing to do would be to use two sessions. One running the background process (the web server) and another to do your development. While it might be possible to log in two sessions with Jade, I’d suggest that you just go ahead an launch Jade twice (two OS processes), and rely on commits in one to make things visible in the other.

James

On Nov 3, 2013, at 6:25 PM, BrunoBB <[hidden email]> wrote:

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Hi James,

This can be called a very fast answer !!!

Thanks for the data.

I was running Seaside from Topaz and developing with Jade because of this. But i was not sure if was doing something wrong.

I will follow your advice and run Jade twice.

Thanks for the clear answer.

Regards,
Bruno

Hi Bruno,

Glad to help. Using Topaz for the “server” and Jade for the development tools is a very reasonable way to balance the tasks. If that is working for you, no need for two Jade processes. The main point is that your description of the situation is how it works—you do need two logins. With GemStone you can’t run the server in the same session where you are doing the development.

James

On Nov 3, 2013, at 7:13 PM, BrunoBB <[hidden email]> wrote:

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Bruno,

To add to James' answer,  I would say that Topaz is probably the best way to launch seaside. In general,  you would like to have all your server management in one place. Of course,  this assumes you want seaside running while your stone is up.

Have fun!

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Hi James,

Excelent, now i understand how it works.

Thanks again...

Regards,
Bruno

Hi Richard,

Ok. Then i will run Seaside from Topaz because can open multiple Topaz using multiple Linux terminals.

For Development i will stay on Jade, because it is awesome.

Thanks to both of you !!!

Regards,
Bruno

Don't forget that you can fork the Topaz process in the shell with "&". Maybe not to start,  but when you want your environment to be more "production"-like, redirect input and output from your Topaz sessions.

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass