In beta 17, you could manipulate headers via the object returned by Call.getConnectorCall(). In beta 18, I'll provide a new mechanism based on Call Converters and maybe in addition connector parameters.
In your case, why would you need to manipulate headers manually? My assumption is that most applications will not require direct access to protocol headers. So, it is better to provide an higher-level view (via the Call object) and leave the container and connectors deal with the protocol-specific logic. One of the issues with the Servlet API was that direct manipulation of headers could prevent some container optimization and lead to portability issues. For example, in your sample application, you were trying to get the "Accept" header I guess. Actually you have all the equivalent information available via the Call.getClient() (SVN version) or via Call.getPreference() (beta 17). Best regards, Jerome > -----Message d'origine----- > De : Chris Winters [mailto:[EMAIL PROTECTED] > Envoyé : lundi 14 août 2006 18:06 > À : [email protected] > Objet : Re: managing URIs? > > Jerome Louvel wrote: > > Sure you can, just set the call.redirectRef property. For the HTTP > > connectors, it will be mapped to the "Location:" response header. > > Great -- I didn't know that property had client-side > visibility. (Still > some jumble in my head about References and how they're used.) > > And that answer works for the 'Location:' header, but what about for > arbitrary headers? For a silly example, say I wanted to send a pithy > saying in a 'X-Fortune' header :-) > > Chris > > -- > Chris Winters ([EMAIL PROTECTED]) > Lead Software Developer > Vocollect Healthcare Systems > > CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and > intended for the addressee(s) only. It may contain privileged and/or > confidential information. If you have received it in error > you are not > authorized to disseminate it in any manner; please delete it and any > copies and reply to the sender that it was misdirected. > > >
