You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by George Christman <gc...@cardaddy.com> on 2014/12/24 21:22:59 UTC
Tapestry URLEncoder
Hi guys, I'm just wondering why Tapestry decided to build their own
URLEncoder over using an existing one like java.net.URLEncoder? I'd
like to clean up my URLs removing a lot of the encoding making them
more search friendly, so I'm wondering what the impact of overriding
the URLEncoder service and implementing a more standard one would be?
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry URLEncoder
Posted by George Christman <gc...@cardaddy.com>.
So do you believe if I use a custom implementation for
PageActivationRequestParameter with the use of the java URLEncoder
that could pose potential issues? I've had it implemented locally for
the past week without any issues, but that's not to say once it's in
production the user base won't find a way to break something.
On Tue, Dec 30, 2014 at 4:19 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> The main motivation behind URLEncoder (side note: really wish I had used
> the term "Transcoder" for these things) was because Jetty, Tomcat, and
> my-weak-understanding-of the servlet spec didn't agree on how and when
> URL-encoded data in the path is decoded.
>
> On Thu, Dec 25, 2014 at 10:49 AM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Wed, 24 Dec 2014 20:09:53 -0200, Dmitry Gusev <dm...@gmail.com>
>> wrote:
>>
>> Hi,
>>>
>>> as far as I know, Tapestry's URLEncoder allows you to not think about
>>> encoding, it forces to UTF-8.
>>>
>>
>> Yep. In addition, it encodes and decodes null and empty string values,
>> something java.net.URLEncoder doesn't do, but Tapestry needs for activation
>> context.
>>
>> Tapestry's URLEncoder is a service as any other, so you can easily
>> override, decorate or advise according to your needs. I'd just suggest you
>> to take a look at how the default implementation works before implementing
>> your own.
>>
>>
>>> Default URLEncoder asks you to specify encoding as a separate parameter,
>>> which you normally pass as another URL parameters, for example, look at
>>> ie/oe parameters that Safari adds to Google request URL when you search
>>> from Safari's address bar:
>>>
>>> https://www.google.com/search?client=safari&rls=en&q=help&
>>> ie=UTF-8&oe=UTF-8
>>>
>>>
>>> On Wed, Dec 24, 2014 at 11:22 PM, George Christman <
>>> gchristman@cardaddy.com>
>>> wrote:
>>>
>>>>
>>>> Hi guys, I'm just wondering why Tapestry decided to build their own
>>>> URLEncoder over using an existing one like java.net.URLEncoder? I'd
>>>> like to clean up my URLs removing a lot of the encoding making them
>>>> more search friendly, so I'm wondering what the impact of overriding
>>>> the URLEncoder service and implementing a more standard one would be?
>>>> Thanks.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>>
>>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
> @hlship
--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry URLEncoder
Posted by Howard Lewis Ship <hl...@gmail.com>.
The main motivation behind URLEncoder (side note: really wish I had used
the term "Transcoder" for these things) was because Jetty, Tomcat, and
my-weak-understanding-of the servlet spec didn't agree on how and when
URL-encoded data in the path is decoded.
On Thu, Dec 25, 2014 at 10:49 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Wed, 24 Dec 2014 20:09:53 -0200, Dmitry Gusev <dm...@gmail.com>
> wrote:
>
> Hi,
>>
>> as far as I know, Tapestry's URLEncoder allows you to not think about
>> encoding, it forces to UTF-8.
>>
>
> Yep. In addition, it encodes and decodes null and empty string values,
> something java.net.URLEncoder doesn't do, but Tapestry needs for activation
> context.
>
> Tapestry's URLEncoder is a service as any other, so you can easily
> override, decorate or advise according to your needs. I'd just suggest you
> to take a look at how the default implementation works before implementing
> your own.
>
>
>> Default URLEncoder asks you to specify encoding as a separate parameter,
>> which you normally pass as another URL parameters, for example, look at
>> ie/oe parameters that Safari adds to Google request URL when you search
>> from Safari's address bar:
>>
>> https://www.google.com/search?client=safari&rls=en&q=help&
>> ie=UTF-8&oe=UTF-8
>>
>>
>> On Wed, Dec 24, 2014 at 11:22 PM, George Christman <
>> gchristman@cardaddy.com>
>> wrote:
>>
>>>
>>> Hi guys, I'm just wondering why Tapestry decided to build their own
>>> URLEncoder over using an existing one like java.net.URLEncoder? I'd
>>> like to clean up my URLs removing a lot of the encoding making them
>>> more search friendly, so I'm wondering what the impact of overriding
>>> the URLEncoder service and implementing a more standard one would be?
>>> Thanks.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>>
>>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Tapestry URLEncoder
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 24 Dec 2014 20:09:53 -0200, Dmitry Gusev <dm...@gmail.com>
wrote:
> Hi,
>
> as far as I know, Tapestry's URLEncoder allows you to not think about
> encoding, it forces to UTF-8.
Yep. In addition, it encodes and decodes null and empty string values,
something java.net.URLEncoder doesn't do, but Tapestry needs for
activation context.
Tapestry's URLEncoder is a service as any other, so you can easily
override, decorate or advise according to your needs. I'd just suggest you
to take a look at how the default implementation works before implementing
your own.
>
> Default URLEncoder asks you to specify encoding as a separate parameter,
> which you normally pass as another URL parameters, for example, look at
> ie/oe parameters that Safari adds to Google request URL when you search
> from Safari's address bar:
>
> https://www.google.com/search?client=safari&rls=en&q=help&ie=UTF-8&oe=UTF-8
>
>
> On Wed, Dec 24, 2014 at 11:22 PM, George Christman
> <gc...@cardaddy.com>
> wrote:
>>
>> Hi guys, I'm just wondering why Tapestry decided to build their own
>> URLEncoder over using an existing one like java.net.URLEncoder? I'd
>> like to clean up my URLs removing a lot of the encoding making them
>> more search friendly, so I'm wondering what the impact of overriding
>> the URLEncoder service and implementing a more standard one would be?
>> Thanks.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry URLEncoder
Posted by Dmitry Gusev <dm...@gmail.com>.
Hi,
as far as I know, Tapestry's URLEncoder allows you to not think about
encoding, it forces to UTF-8.
Default URLEncoder asks you to specify encoding as a separate parameter,
which you normally pass as another URL parameters, for example, look at
ie/oe parameters that Safari adds to Google request URL when you search
from Safari's address bar:
https://www.google.com/search?client=safari&rls=en&q=help&ie=UTF-8&oe=UTF-8
On Wed, Dec 24, 2014 at 11:22 PM, George Christman <gc...@cardaddy.com>
wrote:
>
> Hi guys, I'm just wondering why Tapestry decided to build their own
> URLEncoder over using an existing one like java.net.URLEncoder? I'd
> like to clean up my URLs removing a lot of the encoding making them
> more search friendly, so I'm wondering what the impact of overriding
> the URLEncoder service and implementing a more standard one would be?
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com