Gleb Natapov 52aa0a3f91 db: hold onto write response handler until timeout handler is executed ...

If last response comes after write timeout is triggered, but before
continuation, that suppose to handle it runs the handler can be removed
to earlier and be access from the continuation after deletion. Fix it by
making response handler to be shared pointer instead of unique and
holding to it in timeout continuation.

2015-06-21 13:09:43 +03:00

..

pager

service: Stub paging_state::serialize()

2015-03-11 16:01:13 +01:00

client_state.hh

cql3: Remove QueryHandler class

2015-03-30 14:49:49 +02:00

migration_manager.cc

make storage_proxy object distributed

2015-06-17 15:14:06 +02:00

migration_manager.hh

make storage_proxy object distributed

2015-06-17 15:14:06 +02:00

query_state.hh

service: Remove const qualifier from client_state getter

2015-05-20 15:24:45 +03:00

storage_proxy.cc

db: hold onto write response handler until timeout handler is executed

2015-06-21 13:09:43 +03:00

storage_proxy.hh

db: hold onto write response handler until timeout handler is executed

2015-06-21 13:09:43 +03:00

storage_service.cc

storage_service: Add stop() needed by distributed<>

2015-06-16 15:45:15 +08:00

storage_service.hh

stop storage and messaging services during exit

2015-06-18 15:13:02 +03:00