RE: Disabling the TunnelService

2008-05-22 Thread Jerome Louvel
d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mercredi 21 mai 2008 22:32 À : discuss@restlet.tigris.org Objet : Re: Disabling the TunnelService Hi, Alex Milowski wrote: Would Request.originalRef still have getRemainingPart() returning the unmatched portion? For this I

RE: Disabling the TunnelService

2008-05-21 Thread Jerome Louvel
19 mai 2008 22:19 À : discuss@restlet.tigris.org Objet : Re: Disabling the TunnelService On Mon, May 19, 2008 at 1:31 AM, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Alex, Like Thierry, I have just checked the code again and in trunk the extensions tunnel feature is now off by default

RE: Disabling the TunnelService

2008-05-21 Thread Jerome Louvel
: Rob Heittman [mailto:[EMAIL PROTECTED] Envoyé : vendredi 16 mai 2008 23:46 À : discuss@restlet.tigris.org Objet : Re: Disabling the TunnelService I feel like part of the debate results from the contract of Request.getResourceRef() being unclear. There seem to be at least two differences

Re: Disabling the TunnelService

2008-05-21 Thread Alex Milowski
On Wed, May 21, 2008 at 3:38 AM, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Alex, Thanks for sharing the Atomojo usage details. The TunnelService has been turned on since 1.0 and nobody complained (yet) about the default query parameters (method, charset, encoding, language and media). If

Re: Disabling the TunnelService

2008-05-21 Thread Stephan Koops
Hi, Alex Milowski wrote: Would Request.originalRef still have getRemainingPart() returning the unmatched portion? For this I propose to create a new Reference instance for every call with the baseRef of the updated reference. So they are ever syncronized. best regards Stephan

Re: Disabling the TunnelService

2008-05-19 Thread Thierry Boileau
Hi all, The only thing that is done by default is the update of the user preferences based on query parameters (method and metadata). best regards, Thierry Boileau Hi Alex, If you enable the tunnel service, then I could see (based on whatever it is suppose to do), the URI changing.

Re: Disabling the TunnelService

2008-05-19 Thread Alex Milowski
On Mon, May 19, 2008 at 1:31 AM, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Alex, Like Thierry, I have just checked the code again and in trunk the extensions tunnel feature is now off by default. The idea behind this feature is to have a very simple way for a user to specify, for any

Re: Disabling the TunnelService

2008-05-17 Thread Stephan Koops
Hi Alex, If you enable the tunnel service, then I could see (based on whatever it is suppose to do), the URI changing. Could you give more details? best regards Stephan

Disabling the TunnelService

2008-05-16 Thread Alex Milowski
I now strongly believe that the TunnelService needs to be off by default. I've had to go into *every* single class that extends Application and add this line to my constructor: getTunnelService().setEnabled(false); All of my code is now breaking wherever there is a resource with an

Re: Disabling the TunnelService

2008-05-16 Thread Stephan Koops
Hi Alex, I now strongly believe that the TunnelService needs to be off by default. do you used the most actual version? The extension tunnel is off by default now. * the resource reference should remain the same regardless of whether such filters are enabled. IMO no. It is the