Aeron: Efficient reliable UDP unicast, UDP multicast, and IPC message transport

README.md

To chat with other Aeron users and the contributors.

Efficient reliable UDP unicast, UDP multicast, and IPC message transport. Java and C++ clients are available in this repository via a third party .NET client. All three clients can exchanges messages across machines or on the same machine via IPC very efficiently.

Performance is the key focus. Aeron is designed to be the highest throughput with the lowest and most predictable latency possible of any messaging system. Aeron integrates with Simple Binary Encoding (SBE) for the best possible performance in message encoding and decoding. Many of the data structures used in the creation of Aeron have been factored out to the Agrona project.

For details of usage, protocol specification, FAQ, etc. please check out the
Wiki.

For those who prefer to watch a video then try Aeron Messaging from StrangeLoop 2014. Things have moved on quite a bit with performance and some


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/_JJsjOLgqpw/Aeron

Original article

HTTP/2 makes media loading 3–15 times faster on mobile

Test resultsHTTP/2 demonstrated to be consistently faster then HTTP/1.1 on this test4 times faster on WiFi / 20Mbps cable, average server ping 50ms6 times faster on LTE network, average server ping 90ms15 times faster on 3G network, average server ping 120ms2 times faster on 2G network, average server ping 400msThe reason HTTP/2 is just 2x faster on 2G network is due to EDGE bandwidth constraints as at 170Kbps link rapidly saturates.Left to right: WiFi, LTE, 3GHTTP/1.1 bottlenecksSingle active request per TCP connectioniOS network stack maintains maximum of 4 TCP connections to the server, and multiplexes logical requests between them.Therefore, a maximum of 4 simultaneous requests could be processed at any given moment in time, resulting in poor network link utilization and two main issuesServer is unaware about next client needs until client fully consumed response to preceding request and delivered the following requestIf some responses are slow, they’ll block the


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/iih7J_7-hDM/http-2-makes-media-loading-3-15-times-faster-on-mobile-a455c3e68135

Original article

FreeBSD 11.0-RC1 Now Available

Glen Barber
gjb at FreeBSD.org
Sat Aug 13 01:30:58 UTC 2016
—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

The first RC build of the 11.0-RELEASE release cycle is now available.

Installation images are available for:

o 11.0-RC1 amd64 GENERIC
o 11.0-RC1 i386 GENERIC
o 11.0-RC1 powerpc GENERIC
o 11.0-RC1 powerpc64 GENERIC64
o 11.0-RC1 sparc64 GENERIC
o 11.0-RC1 armv6 BANANAPI
o 11.0-RC1 armv6 BEAGLEBONE
o 11.0-RC1 armv6 CUBIEBOARD
o 11.0-RC1 armv6 CUBIEBOARD2
o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
o 11.0-RC1 armv6 GUMSTIX
o 11.0-RC1 armv6 RPI-B
o 11.0-RC1 armv6 RPI2
o 11.0-RC1 armv6 PANDABOARD
o 11.0-RC1 armv6 WANDBOARD
o 11.0-RC1 aarch64 GENERIC

Note regarding arm/armv6 images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access. Additionally,
the root user password is set to root, which it is strongly
recommended to change the password for both users after gaining
access to the system.

Installer images and memory stick images are available here:

ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/11.0/

The image checksums follow at the end of this e-mail.

If you notice


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/MR3fnp_MZ30/085277.html

Original article

Ardour 5.0 Open Source DAW Officially Released with Tabbed User Interface

Prominent new features of Ardour 5.0 include tabbed user interface, support for control masters (VCAs), support for tempo ramps, support for writing scripts in the Lua programming language


Original URL: http://feedproxy.google.com/~r/linuxtoday/linux/~3/RpaOW9eFPxY/ardour-5.0-open-source-daw-officially-released-with-tabbed-user-interface-160812114519.html

Original article

Gopherpedia: The Gopher Interface to Wikipedia

more about gopherpedia Search Gopherpedia August 14, 2016: The Seduction of Ingmar BergmanAugust 13, 2016: Meteorological history of Hurricane DeanAugust 12, 2016: Turquoise parrotAugust 11, 2016: System Shock 2August 10, 2016: Jerry PentlandAugust 9, 2016: Albert KetèlbeyAugust 8, 2016: SlayerAugust 7, 2016: Wembley Stadium (1923)August 6, 2016: Waddesdon BequestAugust 5, 2016: Harry Trott System Shock 2gopherThe Seduction of Ingmar BergmanSlayerTest (Unix)Turquoise parrotBarack ObamaJava (programming language)Wembley Stadium (1923)Albert KetèlbeyJerry PentlandIngmar BergmanComputer architectureGopher (protocol)overbiteWaddesdon BequestXtermProcessor designHarry TrottLooney Tunes


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/9jq9JjqPrZU/gw

Original article

The Rise and Fall of the Gopher Protocol

An anonymous reader writes: Tim Gihring at MinnPost talks to the creators of what was, briefly, the biggest thing in the internet, Gopher. Gopher, for those who don’t know or have forgotten, was the original linked internet application, allowing you to change pages and servers easily, though a hierarchical menu system. It was quick, it was easy to use, and important for this day and age, it didn’t have Flash.
The article remembers Tim Berners-Lee describing the idea of a worldwide web at a mid-March, 1992 meeting of the Internet Engineering Task Force, at a time when Gopher “was like the Web but more straightforward, and it was already working.”
Gopher became magnitudes more popular — both MTV and the White House announced Gopher sites — leading to GopherCons around the country. Just curious — how many Slashdot readers today remember using Gopher?

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/wH6JWKswVDg/the-rise-and-fall-of-the-gopher-protocol

Original article

SW-delta: an incremental cache for the web

README.md

Continuous delivery is great, but it comes at a price on performances. The more you deliver, the less browsers will use assets they had in cache, because of file versionning. Even if you only changed one letter in a file, it will get downloaded entirely.

Service Workers to the rescue

sw-delta is a project that makes the browser download only the delta ( = diff = incremental download) between the previously cached file and the required version of the file. It is based on the Service Worker API.

How does it work?

Client-side: a Service Worker intercepts every outgoing request. If the url matches one of the configured routes, than the Service Worker will compare the requested version with the version stored in cache. If an update is needed, the Service Worker will update the url to add the known version as a querystring, like this:

Asked url: http://domain.com/js/main-1.2.0.js
Version in cache:


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/8Ifpbgf8vHI/sw-delta

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: