Issue 42 in jayrock: Ability to choose output encoding

5 views
Skip to first unread message

jay...@googlecode.com

unread,
Aug 30, 2011, 2:06:12 PM8/30/11
to jayrock...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 42 by Ionita.A...@googlemail.com: Ability to choose output
encoding
http://code.google.com/p/jayrock/issues/detail?id=42

What new or enhanced feature are you proposing?

The JsonRpcClient's StreamWriter is set to only output in UTF8. It
would be useful to give the programmer the ability to change encoding;
possibly by making use of the HttpWebClientProtocol.RequestEncoding property

What goal would this enhancement help you achieve?

The ability to choose the encoding used over the wire will raise
compatibility when communicating with other Json-RPC implementations and
platforms.

jay...@googlecode.com

unread,
Aug 31, 2011, 6:41:35 AM8/31/11
to jayrock...@googlegroups.com
Updates:
Status: Accepted
Labels: Component-JSON-RPC

Comment #1 on issue 42 by azizatif: Ability to choose output encoding
http://code.google.com/p/jayrock/issues/detail?id=42

(No comment was entered for this change.)

jay...@googlecode.com

unread,
Aug 31, 2011, 4:37:13 PM8/31/11
to jayrock...@googlegroups.com
Updates:
Status: Started
Labels: Milestone-Release1.0

Comment #2 on issue 42 by azizatif: Ability to choose output encoding

jay...@googlecode.com

unread,
Aug 31, 2011, 4:41:23 PM8/31/11
to jayrock...@googlegroups.com
Updates:
Owner: azizatif

Comment #3 on issue 42 by azizatif: Ability to choose output encoding

jay...@googlecode.com

unread,
Aug 31, 2011, 5:23:59 PM8/31/11
to jayrock...@googlegroups.com
Updates:
Labels: -Type-Enhancement Type-Defect

Comment #4 on issue 42 by azizatif: Ability to choose output encoding

jay...@googlecode.com

unread,
Aug 31, 2011, 5:28:01 PM8/31/11
to jayrock...@googlegroups.com
Updates:
Status: Fixed

Comment #5 on issue 42 by azizatif: Ability to choose output encoding
http://code.google.com/p/jayrock/issues/detail?id=42

This issue was closed by revision 62f6ba655677.

Reply all
Reply to author
Forward
0 new messages