uWebsockets.js for FreeBSD
Go to file
Alex Hultman 4c39a1ecfa
Update README.md
2021-01-12 05:45:55 +01:00
.github/workflows Update c-cpp.yml 2021-01-12 00:37:54 +01:00
docs Properly license index.d.ts 2021-01-12 00:50:20 +01:00
examples Wrap missingServerName, update example 2020-08-17 05:41:00 +02:00
misc Add files via upload 2020-06-09 17:32:02 +02:00
src Update uWS, fix warnings 2020-12-19 17:04:24 +01:00
tests Pass Autobahn again 2019-10-09 20:30:50 +02:00
uWebSockets@1acbcaf03a Update uWS to v18.19.0 2021-01-12 02:01:55 +01:00
.gitattributes Don't include js files in language stats 2019-04-10 12:42:00 +02:00
.gitmodules Add uWebSockets submodule 2018-11-04 00:11:12 +01:00
LICENSE Apache 2.0 license 2018-11-15 16:01:49 +01:00
Makefile Make sure to handle double uWS.free 2019-12-21 19:38:02 +01:00
README.md Update README.md 2021-01-12 05:45:55 +01:00
build.c Try and build for ARM64 macOS 11 2020-10-22 23:14:18 +02:00

README.md


Simple, secure[1] & standards compliant[2] web server for the most demanding[3] of applications. Read more...

Language grade: C/C++



💡 Quite simple

µWebSockets.js is a C++ implementation of the WebSocket/HTTP protocols for Node.js, easy to use from JavaScript. Think of it as a much faster alternative to both Socket.IO and Fastify/Express.js; it comes with both router and pub/sub support. Browse the documentation and see the main repo. There are tons of examples but here's the gist of it all:

/* Non-SSL is simply App() */
require('uWebSockets.js').SSLApp({

  /* There are more SSL options, cut for brevity */
  key_file_name: 'misc/key.pem',
  cert_file_name: 'misc/cert.pem',
  
}).ws('/*', {

  /* There are many common helper features */
  idleTimeout: 30,
  maxBackpressure: 1024,
  maxPayloadLength: 512,
  compression: DEDICATED_COMPRESSOR_3KB,

  /* For brevity we skip the other events (upgrade, open, ping, pong, close) */
  message: (ws, message, isBinary) => {
    /* You can do app.publish('sensors/home/temperature', '22C') kind of pub/sub as well */
    
    /* Here we echo the message back, using compression if available */
    let ok = ws.send(message, isBinary, true);
  }
  
}).get('/*', (res, req) => {

  /* It does Http as well */
  res.writeStatus('200 OK').writeHeader('IsExample', 'Yes').end('Hello there!');
  
}).listen(9001, (listenSocket) => {

  if (listenSocket) {
    console.log('Listening to port 9001');
  }
  
});

💪 Unfair advantage

Being written in native code directly targeting the Linux kernel makes it way faster than any JavaScript implementation.

⚔️ Battle proven

We've been fully standards compliant with a perfect Autobahn|Testsuite score since 2016[2]. Companies with everything to lose rely on µWebSockets on a daily basis - we power the trading APIs of Bitfinex.com, handling volumes of about a billion USD every day. Other companies include Trello, where µWebSockets is serving their 50 million users with real-time board updates.

📦 Easily installed

We humbly recommend, for simplicity installing with yarn add uWebSockets.js@uNetworking/uWebSockets.js#v18.14.0 or any such release.

If you have strong opinions regarding the installation process, please read this.

💼 Commercially supported

uNetworking AB is a Swedish consulting & contracting company dealing with anything related to µWebSockets; development, support and customer success.

Don't hesitate sending a mail if you're building something large, in need of advice or having other business inquiries in mind. We'll figure out what's best for both parties and make sure you're not stepping into one of the many common pitfalls.

Special thanks to BitMEX, Bitfinex, Google, Coinbase, Bitwyre and deepstreamHub for allowing the project itself to thrive on GitHub since 2016 - this project would not be possible without these beautiful companies.

👪 A family

µWebSockets.js is the Node.js integration of µWebSockets; the standalone C++ project. If performance is of utter importance, you don't necessarily have to use JavaScript/Node.js but could write apps in C++ using µWebSockets directly. It works exactly the same way, and will offer unbeatable performance for those highly demanding applications. Either way - the two projects both follow the same security testing, compliance testing and receive the same bug fixes and features. They are part of the same family.

🤝 Permissively licensed

Intellectual property, all rights reserved.

Where such explicit notice is given, source code is licensed Apache License 2.0 which is a permissive OSI-approved license with very few limitations. Modified "forks" should be of nothing but licensed source code, and be made available under another product name. If you're uncertain about any of this, please ask before assuming.