[ http://nagoya.apache.org/jira/browse/BEEHIVE-128?page=history ]

Daryl Olander reassigned BEEHIVE-128:
-------------------------------------

    Assign To: Rich Feit  (was: Daryl Olander)

I've moved Bryans change except for one bit of it.  In Scoping there is still a 
call to the URLDecode method.  I didn't want to create another .jar file in 
NetUI.  I believe the options are three at this point:
1) We can create a Beehive Common .jar which should contain the codec URL code. 
 In addition, we may want to move the Scoping and Mutable URL into this same 
.jar.
2) We could put this into the Scoping .jar, creating a dependency on the 
commons codec .jar there.
3) We could move the scoping class into the NetUI util.jar.

I'm assigning this to you Rich because you understand the uses and requirements 
of Scoping which is the remaining place that needs resolving.

> Switch from java.net.URLEncoder/Decoder to 
> org.apache.commons.codec.net.URLCodec for
performance and scalability reasons
> -------------------------------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-128
>          URL: http://nagoya.apache.org/jira/browse/BEEHIVE-128
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI, Web Services (181), Build
>     Reporter: Bryan Che
>     Assignee: Rich Feit
>  Attachments: urlencode-patch.tar.gz
>
> java.net.URLEncoder/Decoder is pretty slow and often bottlenecks 
> pages/servers that do a fair amount of encoding.  We should switch to 
> org.apache.commons.codec.net.URLCodec instead, which is much 
> faster--especially since Beehive already ships commons-codec.  I have a patch 
> that does this and will be uploading it shortly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to