HttpFields is an internal class. (at least the server version of it is, maybe not the jetty-client version)
Also, the changes are likely to handle the new reality in Jetty 9.3, which is HTTP/2 and all it changes/brings to the table. In many cases, deprecation of internal methods and classes is just not possible to completely support. (not sure about this specific case tho) How/Why are you using it? -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Thu, Mar 12, 2015 at 2:46 PM, John Gardiner Myers <[email protected] > wrote: > It's a bit annoying that HttpFields.getStringField(String), etc. was > removed without prior deprecation. The method may be redundant, but such > API changes are a lot easier to deal with when there's a deprecation period. > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
