You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Mindbridge <mi...@yahoo.com> on 2003/10/18 23:55:26 UTC

codec

Hi guys, 

As shown in bug 23511 (http://issues.apache.org/bugzilla/show_bug.cgi?id=23511), the encoding of the URLs needs to be fixed. As suggested by Matt Preston, the codec project in commons does what is needed. One little problem is that the URL encoding class is not in the currently available official version of codec (1.1), but it will be in the next one (1.1.1 or 1.2). The project has been helped a bit to remove the outstanding obsticles, and hopefully the new version will come out soon (but that is not under our control).

So we have the following choices:

1) wait for the official version to come out
2) use the current nightly build now (the code we need is fairly stable according to my testing), and replace it with the official one when it comes out (most likely before we launch the final 3.0)
3) just add the needed class to Tapestry for the time being

Which approach should we take? Personally I would opt for (2), but I am wondering whether you guys would find it acceptable...

Just for reference, the codec jar is about 30K in size.

-mb

Re: codec

Posted by Geoff Longman <gl...@intelligentworks.com>.
Option 2

Geoff
----- Original Message -----
From: "Mindbridge" <mi...@yahoo.com>
To: "Tapestry development" <ta...@jakarta.apache.org>
Sent: Saturday, October 18, 2003 5:55 PM
Subject: codec


Hi guys,

As shown in bug 23511
(http://issues.apache.org/bugzilla/show_bug.cgi?id=23511), the encoding of
the URLs needs to be fixed. As suggested by Matt Preston, the codec project
in commons does what is needed. One little problem is that the URL encoding
class is not in the currently available official version of codec (1.1), but
it will be in the next one (1.1.1 or 1.2). The project has been helped a bit
to remove the outstanding obsticles, and hopefully the new version will come
out soon (but that is not under our control).

So we have the following choices:

1) wait for the official version to come out
2) use the current nightly build now (the code we need is fairly stable
according to my testing), and replace it with the official one when it comes
out (most likely before we launch the final 3.0)
3) just add the needed class to Tapestry for the time being

Which approach should we take? Personally I would opt for (2), but I am
wondering whether you guys would find it acceptable...

Just for reference, the codec jar is about 30K in size.

-mb


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


RE: codec

Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Option #2 works for me.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com

> -----Original Message-----
> From: Mindbridge [mailto:mindbridgeweb@yahoo.com] 
> Sent: Saturday, October 18, 2003 5:55 PM
> To: Tapestry development
> Subject: codec
> 
> 
> Hi guys, 
> 
> As shown in bug 23511 
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=23511), 
> the encoding of the URLs needs to be fixed. As suggested by 
> Matt Preston, the codec project in commons does what is 
> needed. One little problem is that the URL encoding class is 
> not in the currently available official version of codec 
> (1.1), but it will be in the next one (1.1.1 or 1.2). The 
> project has been helped a bit to remove the outstanding 
> obsticles, and hopefully the new version will come out soon 
> (but that is not under our control).
> 
> So we have the following choices:
> 
> 1) wait for the official version to come out
> 2) use the current nightly build now (the code we need is 
> fairly stable according to my testing), and replace it with 
> the official one when it comes out (most likely before we 
> launch the final 3.0)
> 3) just add the needed class to Tapestry for the time being
> 
> Which approach should we take? Personally I would opt for 
> (2), but I am wondering whether you guys would find it acceptable...
> 
> Just for reference, the codec jar is about 30K in size.
> 
> -mb
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: codec

Posted by Erik Hatcher <er...@ehatchersolutions.com>.
On Saturday, October 18, 2003, at 05:55  PM, Mindbridge wrote:
> 2) use the current nightly build now (the code we need is fairly 
> stable according to my testing), and replace it with the official one 
> when it comes out (most likely before we launch the final 3.0)

Use the latest.  I got no problems using CVS builds of open-source 
projects :)

	Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


RE: codec

Posted by David Solis <ds...@legosoft.com.mx>.

> -----Original Message-----
> From: Mindbridge [mailto:mindbridgeweb@yahoo.com]
> Sent: Saturday, October 18, 2003 3:55 PM
> To: Tapestry development
> Subject: codec
> 
> Hi guys,
> 
> As shown in bug 23511
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=23511), the
encoding of
> the URLs needs to be fixed. As suggested by Matt Preston, the codec
> project in commons does what is needed. One little problem is that the
URL
> encoding class is not in the currently available official version of
codec
> (1.1), but it will be in the next one (1.1.1 or 1.2). The project has
been
> helped a bit to remove the outstanding obsticles, and hopefully the
new
> version will come out soon (but that is not under our control).
> 
> So we have the following choices:
> 
> 1) wait for the official version to come out
> 2) use the current nightly build now (the code we need is fairly
stable
> according to my testing), and replace it with the official one when it
> comes out (most likely before we launch the final 3.0)
> 3) just add the needed class to Tapestry for the time being
> 
> Which approach should we take? Personally I would opt for (2), but I
am
> wondering whether you guys would find it acceptable...
> 
I prefer option 2, too.

Regards

D.
> Just for reference, the codec jar is about 30K in size.
> 
> -mb


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org