Changes between Initial Version and Version 4 of Ticket #209
- Timestamp:
- 09/29/2013 05:14:22 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #209
-
Property
Component
changed from
unknown
toappserver
-
Property
Summary
changed from
foolscap assumesinput from stdin will not be unicode
toflappclient assumes input from stdin will not be unicode
-
Property
Component
changed from
-
Ticket #209 – Description
initial v4 1 1 I've registered an application with a flappserver with the --accept-stdin flag. I then invoked the application with unicode type arguments. The flappserver behaves in a difficult to understand manner. 2 2 3 I've traced the data that I input (the unicode) as far as the 4 5 '''appserver.services.Command.remote_feed_stdin''' 6 7 method at which point it was still passing the data around. At some point subsequent to that the data was converted to ''. 3 I've traced the data that I input (the unicode) as far as the {{{appserver.services.Command.remote_feed_stdin}}} method at which point it was still passing the data around. At some point subsequent to that the data was converted to {{{''}}}. 8 4 9 5 This patch zooko wrote should make the client much pickier about the data types it can receive.