You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: HISTORY.md
+15
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,18 @@
1
+
0.3 RC2 / 2012-05-04
2
+
====================
3
+
4
+
* New: Multiple Websocket Transports now fully supported. Switch between Socket.IO (bundled by default) and [SockJS](https://github.com/socketstream/ss-sockjs) (first alpha release) without changing any of your application code
5
+
* New: Socket.IO client library can now be configured (see updated example in README)
6
+
* Live Reload: Working on fixing issues whilst renaming files in VIM (see #227, thanks madscoaducom), fixed issue saving CSS + normal files together
7
+
* Errors in formatting templates (e.g. bad `.jade`) now caught properly
8
+
* Any missing sessions are now automatically recreated (useful when developing without using Redis)
9
+
* New project example code now uses [Nib](http://visionmedia.github.com/nib) instead of custom Stylus helpers
10
+
* Minor refactoring
11
+
* Updated README with video link
12
+
13
+
Note: SocketStream 0.3.0 will be officially launched later in May, along with example apps, screencasts, more documentation and improvements to [www.socketstream.org](http://www.socketstream.org). Read announcement [here](https://groups.google.com/forum/?fromgroups#!topic/socketstream/Y6OIOrJRX7w).
Take a tour of all the new features at http://www.socketstream.org/tour
13
14
15
+
**NEW**[Watch the introductory presentation](http://2011.krtconf.com/videos/owen_barnes) I gave at [KrtConf](http://krtconf.com) last November. Although the first half refers to the previous version (SocketStream 0.2), all the upcoming features I speak about (mid-way through) are now available in SocketStream 0.3.
16
+
14
17
15
18
### Introduction
16
19
@@ -24,6 +27,8 @@ Whilst we have chosen not to support models or reactive templating in the core,
24
27
25
28
SocketStream apps can easily be deployed to [Nodejitsu](http://nodejitsu.com), [EC2 servers](http://aws.amazon.com/ec2) or any other hosting platform supporting websockets (sadly that excludes [Heroku](http://www.heroku.com) for the moment).
26
29
30
+
While it is still early days, our end goal is to ensure SocketStream can be used to power large-scale 'serious' web apps where scalability, flexibility and high availability are key.
31
+
27
32
28
33
#### Quick Facts
29
34
@@ -46,7 +51,7 @@ SocketStream 0.3.0 will be officially launched in May, along with example apps,
46
51
#### Client Side
47
52
48
53
* Works great with Chrome, Safari, Firefox 6 (and above) using native websockets
49
-
* Compatible with older versions of Firefox and IE thanks to configurable fallback transports provided by Socket.IO
54
+
* Compatible with older versions of Firefox and IE thanks to configurable fallback transports
50
55
* Use `require()` and `exports` in your client-side code as you would on the server
51
56
* Define multiple single-page clients by choosing the CSS, JS and client-side templates you wish to serve
52
57
* Integrated asset manager - automatically packages and [minifies](https://github.com/mishoo/UglifyJS) all client-side assets
@@ -62,7 +67,8 @@ SocketStream 0.3.0 will be officially launched in May, along with example apps,
62
67
63
68
#### Server Side
64
69
65
-
* True bi-directional communication using websockets (or [Socket.IO 0.9](http://socket.io) fallbacks). No more slow, messy AJAX!
70
+
* True bi-directional communication using websockets (or websocket fallbacks). No more slow, messy AJAX!
71
+
* Modular Websocket Transports - switch between [Socket.IO](http://socket.io) (bundled by default) or [SockJS](https://github.com/socketstream/ss-sockjs) without changing your app code
66
72
* Easily share code between the client and server. Ideal for business logic and model validation (see Questions below)
67
73
* Request Middleware - enabling session access, authentication, logging, distributed requests and more
68
74
* Effortless, scalable, pub/sub baked right in - including Private Channels
@@ -73,6 +79,7 @@ SocketStream 0.3.0 will be officially launched in May, along with example apps,
73
79
74
80
#### Optional Modules (officially maintained and supported)
75
81
82
+
***[ss-sockjs](https://github.com/socketstream/ss-sockjs)** Use [SockJS](https://github.com/sockjs/sockjs-client) as the websocket transport instead of Socket.IO
76
83
***[ss-console](https://github.com/socketstream/ss-console)** Connect to a live server and call RPC actions or publish events over the REPL / terminal
@@ -83,7 +90,7 @@ SocketStream 0.3.0 will be officially launched in May, along with example apps,
83
90
84
91
SocketStream automatically compresses and minifies the static HTML, CSS and client-side code your app needs and sends this through the first time a user visits your site.
85
92
86
-
From then on all application data is sent and received via the websocket (or Socket.IO fallbacks), instantly established when the client connects and automatically re-established if broken. Normally this will be in [JSON RPC](https://github.com/socketstream/socketstream/blob/master/doc/guide/en/rpc_responder.md) format, but SocketStream 0.3 allows you to use different Request Responders depending upon the task at hand.
93
+
From then on all application data is sent and received via the websocket (or websocket fallbacks), instantly established when the client connects and automatically re-established if broken. Normally this will be in [JSON RPC](https://github.com/socketstream/socketstream/blob/master/doc/guide/en/rpc_responder.md) format, but SocketStream 0.3 allows you to use different Request Responders depending upon the task at hand.
87
94
88
95
All this means no more connection latency, HTTP header overhead, polling, or clunky AJAX. Just true bi-directional, asynchronous, 'streaming' communication between client and server.
89
96
@@ -225,18 +232,28 @@ Install the excellent 'nodemon' module with `sudo npm install -g nodemon` then s
225
232
226
233
##### How can I configure Socket.IO?
227
234
228
-
Like so:
235
+
You may fully configure the Socket.IO server and client libraries like so:
SocketStream works great with [Nodejitsu.com](http://www.nodejitsu.com), as well as custom EC2 / cloud servers. Sadly [Heroku.com](http://www.heroku.com) does not currently support websockets.
239
252
253
+
Tip: If you're deploying to Nodejitsu add the following dependency to your `package.json`:
0 commit comments