Ubuntu
spymemcached package

spymemcached 2.12.3+dfsg-3 source package in Ubuntu

Changelog

spymemcached (2.12.3+dfsg-3) unstable; urgency=medium

  * Team upload.

  [ Debian Janitor ]
  * Apply multi-arch hints. + libspymemcached-java: Add Multi-Arch: foreign.

  [ Jochen Sprickerhof ]
  * Add patch to fix FTBFS (Closes: #1012108)
  * Add missing build dependency on log4j 1.2

 -- Jochen Sprickerhof <email address hidden>  Sun, 26 Feb 2023 17:08:21 +0100

Upload details

Uploaded by:
Debian Java Maintainers
Uploaded to:
Sid
Original maintainer:
Debian Java Maintainers
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc
Mantic release universe misc

Builds

Mantic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
spymemcached_2.12.3+dfsg-3.dsc 2.3 KiB a4e14d4410870185c47fbcf66377a3906de1e6946e678f9945cdbba38c253053
spymemcached_2.12.3+dfsg.orig.tar.xz 148.8 KiB 412059abbc7f784ba7e5b567f5754ddbd8f9046399b189c07aa5bed64bc2b519
spymemcached_2.12.3+dfsg-3.debian.tar.xz 6.1 KiB d410649db135bde3d3cf609298a41948747c3d68d03fd2c5320eed21e10d2c31

Available diffs

No changes file available.

Binary packages built by this source

libspymemcached-java: 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.