Hi Rob, What could be possible is to have a Message#isConfidential() method that would directly test the request's protocol. We would deprecate the Request#setConfidential() method as we wouldn't have to manually maintain the underlying member variable. Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ Co-founder ~ <http://www.noelios.com/> http://www.noelios.com
_____ De : Rob Heittman [mailto:[EMAIL PROTECTED] Envoyé : mercredi 22 octobre 2008 14:40 À : [email protected] Objet : Re: Protocol should determine "confidentiality" of Request Repeating, it's important on the server side. I have a lot of code that depends on examining this. This way the code does not have to explicitly check stuff like ( protocol.equals(Protocol.HTTPS) || protocol.equals(Protocol.RIAP) || ... ) and possibly leave out a confidential communication protocol/pseudoprotocol that the check code is not aware of. It can simply check this property and behave properly (e.g. throw an exception or return forbidden status) if a request that is supposed to be confidential isn't. There is an analogue in the Servlet world that is used similarly. On Wed, Oct 22, 2008 at 8:30 AM, Kevin Conaway <[EMAIL PROTECTED]> wrote: Is the confidential property on the Request (or Message) even necessary? It seems to only be read by the jaxrs module and it doesn't appear to be providing much value there.
