SocketStream>>upToEnd
Markus Fritsche
Fritsche.Markus at gmx.net
Thu Nov 28 11:45:14 UTC 2002
SocketStream>>upToEnd needs contentLenth, however, it's not implemented.
28 November 2002 12:43:33 pm
VM: Win32 - Squeak3.3alpha of 24 January 2002 [latest update: #4967]
Image: Squeak3.4alpha [latest update: #5125]
SocketStream(Object)>>doesNotUnderstand:
Receiver: a SocketStream
Arguments and temporary variables:
aMessage: a Message with selector: #contentLength and arguments: #()
Receiver's instance variables:
socket: a Socket[connected]
inStream: a BufferStream(0)
outStream: a BufferStream(0)
status: a Dictionary(#buffered->true #inDataCount->0 #localAddress->a
ByteArray...etc...
SocketStream>>upToEnd
Receiver: a SocketStream
Arguments and temporary variables:
rest: nil
Receiver's instance variables:
socket: a Socket[connected]
inStream: a BufferStream(0)
outStream: a BufferStream(0)
status: a Dictionary(#buffered->true #inDataCount->0 #localAddress->a
ByteArray...etc...
LIRPCTCPServer>>process:
Receiver: a LIRPCTCPServer
Arguments and temporary variables:
aSocket: a Socket[connected]
ss: a SocketStream
Receiver's instance variables:
connectionHandler: ConnectionHandler port: 8202 [running]
port: nil
[] in LIRPCTCPServer>>value:
Arguments and temporary variables:
aSocket: a Socket[connected]
--- The full stack ---
SocketStream(Object)>>doesNotUnderstand:
SocketStream>>upToEnd
LIRPCTCPServer>>process:
[] in LIRPCTCPServer>>value:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[] in BlockContext>>newProcess
More information about the Squeak-dev
mailing list
|