Polishing
This commit is contained in:
@@ -1196,7 +1196,7 @@ response individually, and instead wait for the combined result:
|
||||
|
||||
The above is merely one example. There are lots of other patterns and operators for putting
|
||||
together a reactive pipeline that makes many remote calls, potentially some nested,
|
||||
inter-dependent, without ever blocking until the end.
|
||||
interdependent, without ever blocking until the end.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
||||
@@ -288,7 +288,7 @@ as the value for the `fieldType` parameter.
|
||||
|
||||
The parameters to any of the above macros have consistent meanings:
|
||||
|
||||
* `path`: The name of the field to bind to (ie "command.name")
|
||||
* `path`: The name of the field to bind to (for example, "command.name")
|
||||
* `options`: A `Map` of all the available values that can be selected from in the input
|
||||
field. The keys to the map represent the values that are POSTed back from the form
|
||||
and bound to the command object. Map objects stored against the keys are the labels
|
||||
|
||||
@@ -978,7 +978,7 @@ The following table describes the properties `CookieLocaleResolver`:
|
||||
| Property | Default | Description
|
||||
|
||||
| `cookieName`
|
||||
| classname + LOCALE
|
||||
| class name + LOCALE
|
||||
| The name of the cookie
|
||||
|
||||
| `cookieMaxAge`
|
||||
|
||||
@@ -84,7 +84,7 @@ In the absence of that, they need to come up with their own conventions.
|
||||
== When to Use WebSockets
|
||||
|
||||
WebSockets can make a web page be dynamic and interactive. However, in many cases,
|
||||
a combination of Ajax and HTTP streaming or long polling can provide a simple and
|
||||
a combination of AJAX and HTTP streaming or long polling can provide a simple and
|
||||
effective solution.
|
||||
|
||||
For example, news, mail, and social feeds need to update dynamically, but it may be
|
||||
|
||||
Reference in New Issue
Block a user