Hi
So you have done a setup ?
Alex
On 2 November 2016 at 08:42, CJ Ess <zxcvbn4038@gmail.com> wrote:
> Probably a better solution then most!
>
> On Fri, Oct 28, 2016 at 10:42 PM, Alex Samad <alex@samad.com.au> wrote:
>>
>> Hi
>>
>> Not really an option in current setup. The rate limit is to stop
>> clients with bad fix servers that spam our fix server.
>>
>> Right now we have a custom bit of java code that that bit rate limits
>> tcp streams..
>>
>> just bought into nginx so looking at stream proxing it through it instead
>> A
>>
>> On 29 October 2016 at 02:48, CJ Ess <zxcvbn4038@gmail.com> wrote:
>> > Cool. Probably off topic, but why rate limit FIX? My solution for heavy
>> > traders was always to put them on their own hardware and pass the costs
>> > back
>> > to them. They are usually invested in whatever strategy they are using
>> > and
>> > happy to pay up.
>> >
>> >
>> >
>> > On Fri, Oct 28, 2016 at 1:29 AM, Alex Samad <alex@samad.com.au> wrote:
>> >>
>> >> Hi
>> >>
>> >> yeah I have had a very quick look, just wondering if any one on the
>> >> list had set one up.
>> >>
>> >> Alex
>> >>
>> >> On 28 October 2016 at 16:15, CJ Ess <zxcvbn4038@gmail.com> wrote:
>> >> > Maybe this is what you want:
>> >> > https://nginx.org/en/docs/stream/ngx_stream_proxy_module.html
>> >> >
>> >> > See the parts about proxy_download_rate and proxy_upload_rate
>> >> >
>> >> > On Thu, Oct 27, 2016 at 11:22 PM, Alex Samad <alex@samad.com.au>
>> >> > wrote:
>> >> >>
>> >> >> Yep
>> >> >>
>> >> >> On 28 October 2016 at 11:57, CJ Ess <zxcvbn4038@gmail.com> wrote:
>> >> >> > FIX as in the financial information exchange protocol?
>> >> >> >
>> >> >> > On Thu, Oct 27, 2016 at 7:19 PM, Alex Samad <alex@samad.com.au>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hi
>> >> >> >>
>> >> >> >> any one setup nginx infront of a fix engine to do rate limiting ?
>> >> >> >>
>> >> >> >> Alex
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> nginx mailing list
>> >> >> >> nginx@nginx.org
>> >> >> >> http://mailman.nginx.org/mailman/listinfo/nginx
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > nginx mailing list
>> >> >> > nginx@nginx.org
>> >> >> > http://mailman.nginx.org/mailman/listinfo/nginx
>> >> >>
>> >> >> _______________________________________________
>> >> >> nginx mailing list
>> >> >> nginx@nginx.org
>> >> >> http://mailman.nginx.org/mailman/listinfo/nginx
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > nginx mailing list
>> >> > nginx@nginx.org
>> >> > http://mailman.nginx.org/mailman/listinfo/nginx
>> >>
>> >> _______________________________________________
>> >> nginx mailing list
>> >> nginx@nginx.org
>> >> http://mailman.nginx.org/mailman/listinfo/nginx
>> >
>> >
>> >
>> > _______________________________________________
>> > nginx mailing list
>> > nginx@nginx.org
>> > http://mailman.nginx.org/mailman/listinfo/nginx
>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
