Hello!
On Fri, Mar 02, 2018 at 09:54:31AM -0500, peanky wrote:
> > Bacause nginx smtp proxy is designed to protect / balance your own
> > smtp backends. If you want to proxy to external smtp servers,
> > consider using other solutions.
>
> Thank you for answer!
> 1. what is the diff between
On Fri, Mar 02, 2018 at 05:30:00AM -0500, sonpg wrote:
Hi there,
> my design is : enduser --> nginx --> sites (sharepoint site:443, web:80;
> 443)
> if server listen in 80 will redirect to 443
That seems generally sensible.
> i try to use stream block but it can't use same port.
Ah: you have
On 02-03-18 17:06, Maxim Dounin wrote:
The question here is - why you want the file to be on disk, and
not just in a buffer? Because you expect the server to die in a
few seconds without flushing the file to disk? How probable it
is, compared to the probability of the disk to die? A more
Hello!
On Fri, Mar 02, 2018 at 08:47:17PM +0100, Valery Kholodkov wrote:
> On 02-03-18 17:06, Maxim Dounin wrote:
> >>> The question here is - why you want the file to be on disk, and
> >>> not just in a buffer? Because you expect the server to die in a
> >>> few seconds without flushing the
On 02/28/2018 03:08 PM, Maxim Dounin wrote:
The question here is - why you want the file to be on disk, and
not just in a buffer? Because you expect the server to die in a
few seconds without flushing the file to disk? How probable it
is, compared to the probability of the disk to die? A more
On 02/28/2018 11:33 PM, Peter Booth wrote:
This discussion is interesting, educational, and thought provoking.
Web architects
only learn “the right way” by first doing things “the wrong way” and
seeing what happens.
Attila and Valery asked questions that sound logical, and I think
there's
On 02/28/2018 11:04 AM, Aziz Rozyev wrote:
While it’s not clear why one may need to flush the data on each http operation,
I can imagine to what performance degradation that may lead of.
I store data on HTTP servers in a distributed manner and have a catalog
of where each file is. If I get back
> Bacause nginx smtp proxy is designed to protect / balance your own
> smtp backends. If you want to proxy to external smtp servers,
> consider using other solutions.
Thank you for answer!
1. what is the diff between "my smtp" and "3rd party smtp" from technical
point of view?
2. which other
On 01/03/2018 11:54, Luciano Mannucci wrote:
It is probably trivial to add an option
to the configuration, something like "autoindex_reverse_sort" (set to
off by default), though I don'nt know if it would be usefull for other
nginx users...
I'd like the option of order by date, "ls -t", "ls
Atilla,
man page quote is related to the Valery’s argument that fsync wont affect
performance, forget it.
It’s nonsense because you’re trying to solve the reliability problem at the
different level,
it has been multiple times suggested here already by maxim and Paul, that it’s
better
to
On 02/28/2018 10:41 PM, Aziz Rozyev wrote:
Without fsyncing file's data and metadata a client will receive a positive
reply before data has reached the storage, thus leaving non-zero probability
that states of two systems involved into a web transaction end up inconsistent.
I understand why
On Fri, 2 Mar 2018 10:33:45 +
James wrote:
> I'd like the option of order by date, "ls -t", "ls -rt". This helps
> because the text order of numbers is "10 11 8 9", see:
>
> http://nginx.org/download/
Well, this is way less trivial than simply add a flag to reverse sort
On 03/02/2018 11:42 AM, Aziz Rozyev wrote:
man page quote is related to the Valery’s argument that fsync wont affect
performance, forget it.
Of course it affects performance. But as for how much: it depends on
many factors. It's possible to build servers where the overall effect
will be
On 02/03/2018 11:33, Luciano Mannucci wrote:
I'd like the option of order by date, "ls -t", "ls -rt". This helps
because the text order of numbers is "10 11 8 9", see:
http://nginx.org/download/
Well, this is way less trivial than simply add a flag to reverse sort
order. It belongs indeed to
On Fri, Mar 02, 2018 at 02:03:36PM +, James wrote:
> On 02/03/2018 11:33, Luciano Mannucci wrote:
>
> >> I'd like the option of order by date, "ls -t", "ls -rt". This helps
> >> because the text order of numbers is "10 11 8 9", see:
> >>
> >> http://nginx.org/download/
> > Well, this is way
On 02/03/2018 14:17, Vladimir Homutov wrote:
Perhaps I should have expressed it as I'd like other people to sort by
date and that isn't going to happen unless it's easy, ie, built in.
autoindex on | off | date | text | ... ;
Well, if you want some interactive sorting, you have to do it in
On Friday 02 March 2018 15:53:07 Haitao Lv wrote:
> # HG changeset patch
> # User 吕海涛
> # Date 1519976498 -28800
> # Fri Mar 02 15:41:38 2018 +0800
> # Node ID 200955343460c4726015180f20c03e31c0b35ff6
> # Parent 81fae70d6cb81c67607931ec3ecc585a609c97e0
> make http2 server
details: http://hg.nginx.org/nginx/rev/265c29b0b8b8
branches:
changeset: 7223:265c29b0b8b8
user: Vladimir Homutov
date: Thu Mar 01 11:42:55 2018 +0300
description:
Access log: support for disabling escaping (ticket #1450).
Based on patches by Johannes Baiter
> А в чём преимущества HTTP2 для Вас? Вы пробовали делать замеры,
> сравнивающие HTTP2 с HTTP1.1?
Для нас преимущество только в мультиплексировании, других преимуществ нет, у
нас просто много параллельных ajax запросов, НТТР 2 push не использовали,
возможно тоже полезная штука, но практики
On Friday, 2 March 2018 13:12:31 MSK S.A.N wrote:
> > А в чём преимущества HTTP2 для Вас? Вы пробовали делать замеры,
> > сравнивающие HTTP2 с HTTP1.1?
>
> Для нас преимущество только в мультиплексировании, других преимуществ нет, у
> нас просто много параллельных ajax запросов, НТТР 2
> От самого мультиплексирования на уровне приложения приемуществ особых
> нет,
> больше недостатков.
Судите сами, на уровне приложения (браузера) сейчас есть два варианта:
НТТР 1х - лимит 8 открытых сокетов на 1 хост, все запросы становятся в эти 8
очередей.
НТТР 2 - в 1 сокет отправляются все
02.03.2018, 16:16, "S.A.N" :
>> От самого мультиплексирования на уровне приложения приемуществ особых
>> нет,
>> больше недостатков.
>
> Судите сами, на уровне приложения (браузера) сейчас есть два варианта:
>
> НТТР 1х - лимит 8 открытых сокетов на 1 хост, все
> Но к вебсокетам все это никакого отношения не имеет, не так ли?
Да, вы правы, мой ответ был в контексте НТТР запросов.
Польза для WebSocket использовать сокет Н2, в том что он будет держать
открытым сокет, который использует ajax запросы.
У нас может быть 20-30 ajax потом минут 15 тишина, юзер
23 matches
Mail list logo