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
If you are building directly on top of strong-remoting without LoopBack,
11
+
then please [open a new GitHub issue](https://github.com/strongloop/strong-remoting/issues/new)
12
+
to discuss the specifics.
13
+
14
+
See also [Module Long Term Support Policy](#module-long-term-support-policy)
15
+
below.
16
+
3
17
## Overview
4
18
5
19
Objects (and, therefore, data) in Node applications commonly need to be accessible by other Node processes, browsers, and even mobile clients. Strong remoting:
@@ -16,13 +30,16 @@ Also see the <a href="http://loopback.io/doc/en/lb2/Strong-Remoting.html">offici
16
30
17
31
For higher-level transports, such as REST and Socket.IO, existing clients will work well. If you want to be able to swap out your transport, use one of our supported clients. The same adapter model available on the server applies to clients, so you can switch transports on both the server and all clients without changing your application-specific code.
18
32
19
-
### Supported versions
33
+
## Module Long Term Support Policy
34
+
35
+
This module adopts the [Module Long Term Support (LTS)](http://github.com/CloudNativeJS/ModuleLTS) policy, with the following End Of Life (EOL) dates:
0 commit comments