[
https://issues.jboss.org/browse/GTNCOMMON-14?page=com.atlassian.jira.plug...
]
Chris Laprun commented on GTNCOMMON-14:
---------------------------------------
See
http://tools.ietf.org/html/rfc4329 for more details (section 4.2 in particular)
Update support for Mime Types
-----------------------------
Key: GTNCOMMON-14
URL:
https://issues.jboss.org/browse/GTNCOMMON-14
Project: GateIn Common
Issue Type: Feature Request
Reporter: Matt Wringe
Some of the mime type handling is done in the common module (see the
org.gatein.common.net.media package). In the GateIn portal and WSRP module (and probably
in other modules as well) mime types are also partially handled.
What we need is to handle more of the mime types in the common module or use a third
party mime type library.
What we would need done is:
1) determine if we are dealing with text content or binary content.
-We cannot assume that if the mime type is not 'text' then we are dealing with
binary content. 'application/javascript' or 'application/emcascript'
should be considered as text. We need to create a list to determine this (and include the
non standard x-* types)
-We also cannot determine if we are dealing with text or binary content based on if we
receive characters or bytes back. The text content can be returned as a byte array.
2) properly determine the encoding of text content. The encoding type can be determined
by looking at the first few bytes of data (this is optional), we are currently not looking
into bytes to determine the encoding.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira