Re: [Flock-devel] Feature Requests: Use a flock.properties config file instead of system properties

[Ian F. <hom...@ad...>]

Sorry I meant to reply much quicker. I'm the one using Flock still :)

I wanted to say, Flock makes for a great webservices cache as well as 
RSS aggregator.

I also keep meaning to submit a new XSL which has better RSS 2.0 
support, I attempted to support ATOM 0.3 too, but can never quite find 
the time.

Cheers,

Ian Forrester - cubicgarden.com

Zsombor wrote:

>It's good to hear, that someone still use the program, however the
>original authors have lost their enthusiasm long time ago.If I can
>believe in the CVS change logs, more than 2 year passed since our last
>release :-) Anyway, i've commited the necessary changes to the CVS, so
>if you can do a full check out, and do a 'maven war' then you will have
>a fresh flock-0.7. The generated war will contain a
>WEB-INF/flock.properties file, in which you can customize the flock
>storage directory, with the store.directory property.
> I hope phraktle will update the website, because I cant remember how to
>do that :-)
>
>BR,
>	Zsombor
>
>
>
>2005-03-29, k keltezéssel 12:25-kor ad...@in... ezt írta:
>  
>
>>I'm with a hosting company that offers Java hosting (on Tomcat). In our
>>normal configuration, we run a shared Tomcat instance per server (shared
>>JVM). This is perfectly acceptable to many customers nowadays, and lets us
>>offer a more affordable Java hosting service.
>>
>>A common problem with open-source Java products is the tendency to assume
>>everybody's on a private JVM, and so to rely on system properties for
>>application configuration. I think that goes against the purpose of "system"
>>(not webapp) properties anyway, and it causes a lot of problems in a
>>shared-JVM environment. This is a show-stopper with Flock, because the
>>default location of Flock's home directory is /username/.flock. This is
>>problematic because Tomcat runs under the same username for all users. It
>>seems the only way to set this parameter is through the flock.home system
>>property, which is also a problem, because this will again be shared by all
>>users. So I'm essentially limited to one installation of flock per server.
>>
>>I can see reasons why you might want several Flock installations (in
>>different Webapps, for example), even on a dedicated JVM setup, so I think
>>it's too limiting to set this only by system property. I think you really
>>need to allow a flock.properties file that can be placed in WEB-INF/classes
>>for example, so that flock.home can be specified separately for each webapp.
>>
>>Please let me know if this is a possibility, as I have a user who is eager
>>to run Flock in his account.
>>
>>Gratefully,
>>
>>Pete Cassetta
>>interAdvantage Administrator
>>ad...@in...
>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Flock-devel mailing list
>>Flo...@li...
>>https://lists.sourceforge.net/lists/listinfo/flock-devel
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Flock-devel mailing list
>Flo...@li...
>https://lists.sourceforge.net/lists/listinfo/flock-devel
>
>
>  
>