At 12:09 2000-12-20, [EMAIL PROTECTED] wrote:
>ingo schuster wrote:
> >
> > If you want to use Jetspeed with a proxy and don't want to use a proxy for
> > *all* connections (see problems in my note yesterday), I could offer a
> patch.
> >
> > Question: Should I commit this in the alpha 1 (it's more a new feature that
> > a bug fix), wait for alpha 2 or don't you like it at all?
> >
>
>I'm +1 for the patch idea.
>-1 for the implementation :
>The URLManager init() should be in charge of collecting all its operational
>parameters through TurbineServices.getProperties() in current Jetspeed
>Turbine
>or ResourceService.getResources() in latest Turbine.
>
>The fetcher can then use the collected value either through direct access
>to the Service implementation if the feature is implementation dependent
>or added to the Service interface if the method should be implemented by all
>service implementations (I think the proxy issue is generic enough to be
>put in the Service interface).
>
>And also, if you use TurbineResources, you have a whole lot of methods
>like getInt() so you don't need to do a parseInt( getString() ).
Absolutely true, I'll just got this patch from my colleage, did'nt check
the code quality.
>I think this patch will wait for alpha 2 unless you're a *very* quick
>coder. :)
Ok, alpha2 is soon enough.
ingo.
>--
>Rapha�l Luta - [EMAIL PROTECTED]
>Vivendi Universal Networks - Services Manager / Paris
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Search: <http://www.mail-archive.com/[email protected]/>
>List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
