RE: [Rabbit-proxy-users] SQL authentication

[Richard M. <ri...@sy...>]

Robo,

   I would venture to say no caching.  One of the reasons for using a SQL
backend is for real time updates without having to "reload" the server
software.   As Luis pointed out, most software that uses SQL backends have
options to specify the SQL server, username, password, database and some
even go as far as to letting you write your own SELECT statement. (As shown
in Luis' post)   I don't know how useful this feature would be to most
people, but it would be a nice feature to have listed on the website.  ;)
(I would use it though...)



       Richard Dean Marriner II
SYIX.COM  --=--  Network Administrator
530-755-1751x206 - richard at syix.com
 

> -----Original Message-----
> From: rab...@li... 
> [mailto:rab...@li...] On 
> Behalf Of Robert Olofsson
> Sent: Thursday, May 05, 2005 4:50 AM
> To: Luis Soltero
> Cc: Richard Marriner; rab...@li...
> Subject: Re: [Rabbit-proxy-users] SQL authentication
> 
> Luis Soltero wrote:
> 
> >Specifying a connection string and an sql query string in 
> rabbit the conf would be wonderful.
> >  
> >
> This is not possible right now. Writing a filter to handle it 
> will not take
> long.
> 
> How long should the data be cached in rabbit? or do you want rabbit to
> ask the database for every request it gets? Should negative responses
> be cached as well?
> 
> /robo
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 
> great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Rabbit-proxy-users mailing list
> Rab...@li...
> https://lists.sourceforge.net/lists/listinfo/rabbit-proxy-users
>