Mohammad DAMT wrote:

>> > * handler
>> > - Added "ServerList" directive in config file, typical use:
>> >
>> > Extension fcgi {
>> >       Handler fastcgi {
>> >               ServerList /tmp/sock
>> >               ServerList 127.0.0.1:8090
>> >               ServerList 127.0.0.1:8070
>> >       }
>> > }
>>
>>   I would use "Server" rather than "ServerList", the meaning is the
>>   same and we don't need to add one more reserved word to the grammar.
>
> If we use "Server" then is it possible to load it to a list_t?

  Yeah, sure.. try just to change the token "ServerList" for the
  "Server" one, it should work.

>> > - I also haven't touch interpreter part since it is string type
>> > directive, so only one Interpreter will be allowed, I guess. Should
>> > each (local) server requires separate Interpreter directive?
>>
>>   Ummm.. I think so.  That was meant to be the way in which the server
>>   could spawn new servers if necessary.
>
> Although this is only possible with local fcgiserver, what do you
> think if the config should look like this:
>
> Extension fcgi {
>       Handler fastcgi {
>                Server {
>             Socket /tmp/sock
>             Interpreter "/to/some/path/php-fcgi"
>            }
>
>                Server {
>             Server 127.0.0.01:8090
>             Interpreter "/to/some/path/php-fcgi"
>            }
>
>                Server {
>             Server some.remote.host:8090
>            }
>        }
>  }

  What about something like this?

  Extension fcgi {
    Server /tmp/sock {
      Interpreter /usr/bin/whatever
    }

    Server 127.0.0.1:8090 {
      Interpreter /usr/bin/whatever2
    }

    Server 127.0.0.1:8091 {
      Interpreter /usr/bin/whatever3
    }
  }

> Does the grammar now support this kind of thing?

  We will need to do a couple of minor changes.. but, yeah, basically
  it is supported.

>> > Please check whether I'm on a correct track.
>>
>>   Yeah, I think so.  BTW, when would you like me to commit your patch
>>   to start working on the SVN and releasing the changes in each
>>   version?  Could we schedule it for 0.5.0?
>
> That would be ok.

  Okay, I am going to apply it. :-)

--
Greetings, alo.
http://www.alobbs.com

_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to