Skip to content

Conversation

@mwinter69
Copy link

Get the charset of a run and use it whenever we need to convert the String to a byte array.

properly get displayname of node (jenkinsci#38)
Get the charset of a run and use it whenever we need to convert the
String to a byte array
}

@Override
public void setCharset(Charset charset)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make it explicit what the purpose here is? We have the charset using during the build, and the charset used to encode the outgoing messages.

Those two do not necessarily need to be the same.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added javadoc to describe the purpose

@jakub-bochenski
Copy link

jakub-bochenski commented Dec 29, 2017

For backends that use HTTP transport (Logstash, ES) it would be nice to use the charset mime type parameter (e.g. application/json; charset=UTF-8 for the output messages (see also #41).
Do you think this is feasible?

@mwinter69
Copy link
Author

For this PR I would keep as is. Making mimetype and charset configurable should be done once we have completed the refactoring of configuration

@jakub-bochenski jakub-bochenski merged commit 9046206 into jenkinsci:master Dec 29, 2017
@mwinter69 mwinter69 deleted the charset branch December 30, 2017 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants