rohc team mailing list archive

Thread
Date

Re: Migrating from 1.7.0 to 2.1.0

To: "rohc@xxxxxxxxxxxxxxxxxxx" <rohc@xxxxxxxxxxxxxxxxxxx>
From: Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
Date: Tue, 12 Dec 2017 02:35:26 +0000
Accept-language: en-NZ, en-US
Authentication-results: spf=none (sender IP is ) smtp.mailfrom=yakir.matusovsky@xxxxxxxxxxx;
In-reply-to: <BF70756A-02CB-4A58-B768-27C8F4ED3496@mimomax.com>
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99
Thread-index: AQHTcZ1belgtIZgykEOXcFd9p3W2Z6M/2mwA
Thread-topic: Migrating from 1.7.0 to 2.1.0

Sorry please ignore my question regarding rohc_decomp_context_free_e().
This was an internally added wrapper to context_free()…

Regards,
Yakir

From: Yakir Matusovsky <yakir.matusovsky@xxxxxxxxxxx>
Date: Sunday, 10 December 2017 at 10:57 PM
To: "rohc@xxxxxxxxxxxxxxxxxxx" <rohc@xxxxxxxxxxxxxxxxxxx>
Subject: Migrating from 1.7.0 to 2.1.0

Hi

Function rohc_decomp_context_free_e() was in 1.7 and in the recent stable release it is obsolete.
I’d found context_free() with similar prototype however it is private to decomp module.
If wanted to maintain contexts as previously from my app, could I use context_free()?

Thanks ahead.

Regards
Yakir

References

Migrating from 1.7.0 to 2.1.0
From: Yakir Matusovsky, 2017-12-10