unit.git, branch 1.14.0 Universal Web Application Server Generated Dockerfiles for Unit 1.14.0. 2019-12-26T14:03:21+00:00 Valentin Bartenev vbart@nginx.com 2019-12-26T14:03:21+00:00 be8589d92580ff0bfc740f3d6b496fad411a050f 






Added version 1.14.0 CHANGES.
2019-12-26T14:03:21+00:00

Valentin Bartenev
vbart@nginx.com

2019-12-26T14:03:21+00:00

94032333282ebf8d0d8ed6f344fe2b1dcb7cffd1












Go: changing import name for "unit.nginx.org/go".
2019-12-25T17:00:32+00:00

Max Romanov
max.romanov@nginx.com

2019-12-25T17:00:32+00:00

693a458b4ea87b7b387bd9d094de2b42be7ecdbd

This patch includes packaging changes - update unit-go installation
directory.





This patch includes packaging changes - update unit-go installation
directory.







Using the 64-bit Linux capability mode when available.
2019-12-16T17:12:09+00:00

Tiago Natel de Moura
t.nateldemoura@f5.com

2019-12-16T17:12:09+00:00

eced72ba25a1aced3553ac4e8499c4c2befd2a91

For backward compatibility, the Linux capabilities macros exposes v1 semantics
(32-bit) by default.  We probe the version at runtime (because of pre-compiled
binaries) but the kernel syscall API is conservative and it doesn't return a
64-bit capability version if the input version is v1.

This patch suppress the kernel > 5.0 dmesg log below:

  capability: warning: 'unitd' uses 32-bit capabilities (legacy support in use)





For backward compatibility, the Linux capabilities macros exposes v1 semantics
(32-bit) by default.  We probe the version at runtime (because of pre-compiled
binaries) but the kernel syscall API is conservative and it doesn't return a
64-bit capability version if the input version is v1.

This patch suppress the kernel > 5.0 dmesg log below:

  capability: warning: 'unitd' uses 32-bit capabilities (legacy support in use)







Tests: routing by listener address.
2019-12-24T13:59:58+00:00

Axel Duch
axel.duch@nginx.com

2019-12-24T13:59:58+00:00

96a9a790a00c0d0dc4c3f71ced0a6e1ebeca72f7












Router: introducing routing on listener address.
2019-12-24T13:59:58+00:00

Axel Duch
axel.duch@nginx.com

2019-12-24T13:59:58+00:00

1a76371499d60856e000bd560a30389ad442b13a












Tests: routing by client address configuration.
2019-12-24T13:58:22+00:00

Axel Duch
axel.duch@nginx.com

2019-12-24T13:58:22+00:00

ee8fa5d46707d92ed2fbdee193b1ea32281716b1












Router: introducing routing on client address.
2019-12-24T13:58:10+00:00

Axel Duch
axel.duch@nginx.com

2019-12-24T13:58:10+00:00

8677bf8d41e002310971fddbc5e45c64034afc2f












Go: introducing SHM_ACK observer.
2019-12-24T15:04:21+00:00

Max Romanov
max.romanov@nginx.com

2019-12-24T15:04:21+00:00

26ee4cb6c8a2248f0f7c99d8c622c86a52bf197a

Each request processed in a separate goroutine.  In case of OOSM state,
during response write, request goroutine blocks on channel which waits
event from main thread about SHM_ACK message from router.





Each request processed in a separate goroutine.  In case of OOSM state,
during response write, request goroutine blocks on channel which waits
event from main thread about SHM_ACK message from router.







Node.js: implementing output message drain using SHM_ACK feature.
2019-12-24T15:04:17+00:00

Max Romanov
max.romanov@nginx.com

2019-12-24T15:04:17+00:00

763bdff4018ec35de8383273d366160adebb6021

ServerResponse.write() method tries to write data buffer using libunit
and stores buffers to write in a Server-wide output queue, which is
processed in response to SHM_ACK message from router.

As a side effect 'drain' event implemented and socket.writable flag
reflect current state.





ServerResponse.write() method tries to write data buffer using libunit
and stores buffers to write in a Server-wide output queue, which is
processed in response to SHM_ACK message from router.

As a side effect 'drain' event implemented and socket.writable flag
reflect current state.