bug in FTPClient?

Im trying to use monticello to connect to an FTP based monticello server.

but when i try to connect i get a message not understood error.  It seems
that Socket>>connectTo:port: is sending #port: to a ByteArray.  the
bytearray is the ip address octets, but it clearly doesnt understand
#port:

this works fine for http based servers, but for an ftp server it gets this
exception, is anyone else seeing this?




--
[hidden email]

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

I have been using the FTP connection in Monticello on both a Windows  
machine and Mac with no problems. I have not explored that code enough  
to offer any insight. Good luck.
-Cam

On Apr 24, 2009, at 11:15 AM, Joseph T. Bore wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

i did a search on the bugs/issues page and it turns out that im not the
only one seeing this.  Issue #753 is the exact same problem.

can i ask you any more detail on what version and what updates you are
running?




On Fri, 24 Apr 2009, Cameron Sanders wrote:

--
[hidden email]

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sure.
I have used an FTP connection for Monticello in several different  
versions of the vm: 3.9, 3.10.2, and now the closure-vm with Cassou's  
dev-image from last week with no updates -- i cut-n-pasted the mouse  
fixes for the mac after that first note. Images used for 3.9 and 3.10  
included both Pharo and straight-up Squeak.  (There is a chance I used  
it under 3.8, but... I am not certain.)

Oh, my Mac work has all be in the last three weeks, starting with a  
Core image 3 weeks ago.

Let me get into the debugger...
--
Socket>>connectTo: hostAddress port: port
        "Initiate a connection to the given port at the given host address.
        Waits until the connection is established or time outs."
        NetNameResolver useOldNetwork
                ifTrue: [self connectTo: hostAddress port: port  
waitForConnectionFor: Socket standardTimeout]
                ifFalse: [
                        hostAddress port: port.
                        self connectTo: hostAddress]
--
Host address is an instance of SocketAddress for me.

The stack is:
...
Socket>>connectTo:port:
SocketStream class>>openConnectionToHost:port:
FTPClient(ProtocolClient)>>ensureConnection
FTPClient(ProtocolClient)>>openOnHost:port:
FTPClient class(ProtocolClient class)>>openOnHost:port:
FTPClient class(ProtocolClient class)>>openOnHostNamed:port:
...

And the code for the latter is...
FTPClient class(ProtocolClient class)>>
openOnHostNamed: hostName port: portNumber
        | serverIP |
        serverIP := NetNameResolver addressForName: hostName timeout: 20.
        ^self openOnHost: serverIP port: portNumber

So... I would test that message to NetNameResolve in a workspace.  
Also, SocketStream openConnectionToHost: self host port: self port  
(see FTPClient>>ensureConnection).

Good luck.
Cam

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project