[CRIU] service: one connection -- multiple requests

[Ruslan Kuprieiev]

On 24.11.2013 00:10, Pavel Emelyanov wrote:
> On 11/23/2013 06:50 PM, Ruslan Kuprieiev wrote:
>> I have noticed that if program does something like this:
>>       -- ....
>>       -- ask to dump itself
>>       -- ask service to do something else
>>       -- ....
>>
>> and then we are trying to restore it -- it will fail, as the service
>> socket(that was created especially for this process) will be closed.
>> Without multirequesting everything will be fine, as for every request
>> the new one socket will be created.
>> I think we shouldn't reject multirequesting, because of it's goals: it
>> is fast and a bit easy to work with. Maybe we should give user a choose
>> somehow?
>> .
> I think that for muli-request we should extend the criu_req request
> with "optional bool more_requests_will_follow;" or some better name.

Why not "multirequest"? Or it is lame?

> The service will decide itself whether it can handle more requests
> and act respectively. E.g. multi bit in DUMP_ME request should be
> rejected.