File: control

package info (click to toggle)
spymemcached 2.12.3+dfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 2,072 kB
  • sloc: java: 19,420; xml: 920; sh: 87; makefile: 17
file content (61 lines) | stat: -rw-r--r-- 2,465 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
Source: spymemcached
Section: java
Priority: optional
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders:
 Andrius Merkys <merkys@debian.org>,
 Christopher Hoskin <mans0954@debian.org>,
Build-Depends:
 debhelper-compat (= 12),
 default-jdk,
 maven-debian-helper (>= 2.1),
 memcached <!nocheck>,
 net-tools <!nocheck>,
 procps <!nocheck>,
Build-Depends-Indep:
 junit4 <!nocheck>,
 libdropwizard-metrics-java,
 libjmock-java <!nocheck>,
 libspring-beans-java,
Standards-Version: 4.4.1
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/java-team/spymemcached.git
Vcs-Browser: https://salsa.debian.org/java-team/spymemcached
Homepage: http://www.couchbase.org/code/couchbase/java

Package: libspymemcached-java
Architecture: all
Depends:
 ${maven:Depends},
 ${misc:Depends},
Suggests:
 ${maven:OptionalDepends},
Description: simple, asynchronous, single-threaded memcached client
 Spymemcached is a simple, asynchronous, single-threaded memcached client
 written in Java, featuring:
 .
  *   Efficient storage of objects. General serializable objects are stored in
      their serialized form and optionally compressed if they meet criteria.
      Certain native objects are stored as tightly as possible (for example, a
      Date object generally consumes six bytes, and a Long can be anywhere from
      zero to eight bytes).
 .
  *   Resilient to server and network outages. In many cases, a client
      operation can be replayed against a server if it goes away and comes
      back. In cases where it can't, it will communicate that as well. An
      exponential backoff reconnect algorithm is applied when a memcached
      becomes unavailable, but asynchronous operations will queue up for the
      server to be applied when it comes back online.
 .
  *   Operations are asynchronous. It is possible to issue a store and continue
      processing without having to wait for that operation to finish. It is even
      possible to issue a get, do some further processing, check the result of
      the get and cancel it if it doesn't return fast enough.
 .
  *   There is only one thread for all processing. Regardless of the number of
      requests, threads using the client, or servers to which the client is
      connected, only one thread will ever be allocated to a given
      MemcachedClient.
 .
  *   Aggressively optimized. There are many optimizations that combine to
      provide high throughput.