File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
content/develop/clients/jedis Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -57,7 +57,7 @@ to learn how to use this technique with Jedis.
57
57
58
58
[ Client-side caching] ({{< relref "/develop/clients/client-side-caching" >}})
59
59
involves storing the results from read-only commands in a local cache. If the
60
- same command is executed again later, the result can be obtained from the cache,
60
+ same command is executed again later, the results can be obtained from the cache,
61
61
without contacting the server. This improves command execution time on the client,
62
62
while also reducing network traffic and server load. See
63
63
[ Connect using client-side caching] ({{< relref "/develop/clients/jedis/connect#connect-using-client-side-caching" >}})
@@ -129,7 +129,7 @@ inactivity.
129
129
130
130
Redis handles many errors using return values from commands, but there
131
131
are also situations where exceptions can be thrown. In production code,
132
- you should handle
132
+ you should handle exceptions as they occur.
133
133
134
134
The Jedis exception hierarchy is rooted on ` JedisException ` , which implements
135
135
` RuntimeException ` . All exceptions in the hierarchy are therefore unchecked
You can’t perform that action at this time.
0 commit comments