Hey Milan, I never thought you were a "moron" - why would I from just two e-mails? You asked a question, and I spent my precious time trying to give you a helpful answer, so I didn't appreciate that attitude.
Yes, the Node is a persistent object in the database and the server commits its hostname - using NetNameResolver localHostName. See MagmaServerConsole>>#thisLocation and you can browse senders from there if you're interested. It sounds like you need to set up a hostname for your machine.
- Chris
On Thu, Aug 11, 2011 at 12:17 PM, Milan Mimica milan.mimica@gmail.com wrote:
Would you please stop assuming I'm a moron and read again what I wrote? Here, I'll write it down again, perhaps more clear this time:
| mySession | mySession := (MagmaRemoteLocation host: '217.172.181.118' port: 51001) newSession. Transcript show: mySession primaryLocation; cr. " --> says a MagmaRemoteLocation magma:217.172.181.118:51001" mySession connectAs: 'chris'. Transcript show: mySession primaryLocation; cr. " --> says a MagmaRemoteLocation magma:localhost:51001" mySession root. " --> fails because it's trying to connect to localhost " mySession disconnect.
I just doesn't look right, does it? I did some debugging, and what happens is that in MagmaSession>>primConnect repository definition is overridden by something which is, I assume, returned by the server.
Chris Muller wrote:
Magma uses NetNameResolver to convert the hostname you provide to an IP.
On Wed, Aug 10, 2011 at 4:35 PM, Milan Mimica milan.mimica@gmail.com wrote:
Yes, I figured I can run it blind and that's fine. But I've got another problem I just can't make sense out of it. Running this code on my machine: | mySession | mySession := (MagmaRemoteLocation host: 'my.server.ip.addr' port: 51001) newSession. mySession connectAs: 'chris'. mySession root. mySession disconnect.
I am getting this error: ConnectionTimedOut: Cannot connect to 127.0.0.1:51001
What confuses hell out of me is that it tries to connect to localhost when sending #root to session object. Why? How?
Chris Muller wrote:
Ok, would you mind finding out whether Pharo supports writing to stdout? It may need to be upgraded to have the same capabilities as Squeak.
You may want to consider just deploying your Magma servers on Squeak. You could still use Pharo for your web-server if you want..
Another option, if you feel you must run Pharo, you could comment out that code which accesses stdout and run "blind" - no console messages...
- Chris
On Wed, Aug 10, 2011 at 3:25 PM, Milan Mimica milan.mimica@gmail.com wrote:
Chris Muller wrote:
- I don't know what OS you're using but.. since you are using Magma, you already have MaCommandLineProcessor in your image. It is +very convenient+ for interfacing with Squeak from the Linux command-line.
I'm getting: MessageNotUnderstood: StandardFileStream class>>stdout
at CommandLineProcessor class >> do
Using Pharo 1.2
-- Milan Mimica http://sparklet.sf.net
-- Milan Mimica http://sparklet.sf.net
-- Milan Mimica http://sparklet.sf.net