Hi, I'm writing you the weekly report a little earlier than expected, because I might be not able to do it on Sunday. This week was busy of testing and writing code.
I designed some of the data structures that I will need. One of them is a associative array (dictionary) that is implemented as a hash table. You may check the code in dictionary.c if you are interested how it's working. I designed some of the data structures that I will need and picked the hooks that I will need to make the plugin work and started designing and implementing them. Also I started with making the configuration file. I'm providing you some sample configuration file so you may send me some feedback and feature requests. ## ## Proxy-Reverse configuration. ## ## This is example Proxy-Reverse configuration. ## Currently is in proposed (not final) state ## #[PROXY_DEFAULTS] ##Here we can put default key,values that will be used for all the PROXY_ENTRY. ##The values in PROXY_INSTANCE will overwrite the PROXY_DEFAULTS # ServerList 127.0.0.1:8080 remote:80 # LoadBalancing First-Alive # [PROXY_ENTRY] ##Every proxy configuration may have its own Match Rules, Load Balancing or different destination hosts and etc. # Match /*.php # [PROXY_ENTRY] # ServerList RemoteStatic:80 10.10.10.4:80 # LoadBalancing Round-Robin # Match /*.jpg # Match /*.png # Match /*.css # Match /*.js # Match /*.html My idea of making it this way is to be able to use monkey as a load balancer for different cases and by using 1 monkey proxy for different backend cases. Suggestions and Feedback on this early stage will be highly appreciated. Thank you. Regards, Nikola Nikov
_______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
