I don't think there is any near-term plans to implement OutOfProc,
however it WAS in the original design docs as an oft-requested feature,
so I suspect it is something that will possibly come back in the future.
As far as removing it, I personally wouldn't see an issue with removing
OutOfProc as it sits, since the current implementation is a wrapper
instance only, but that would be up to Jon Cruz and the OIC to decide
whether this feature is beneficial.
On Mon, 2015-11-30 at 23:47 +0000, Rahul, Rahul wrote:
> While going through the code, I found that we have 2 options for
> ServiceType ? InProc and OutOfProc defined in OCApi.h
>
>
>
> This is the 1st option when creating a PlatformConfig and it seems
> like only InProc is supported. If I change it to OutOfProc in
> simpleclient example
>
> PlatformConfig cfg
>
> {
>
> ServiceType::OutOfProc, ModeType::Client, "0.0.0.0", 0,
> QualityOfService::LowQos
>
> };
>
> ,
>
> it crashes with the following dump:
>
>
>
> terminate called after throwing an instance of 'OC::OCException'
>
> what(): result_guard(): 32: Not Implemented
>
> Aborted (core dumped)
>
>
>
> My question is if there is any plan for implementing OutOfProc? If
> not, is it safe to remove it form the Iotivity codebase?
>
>
>
> Thanks,
>
> Rahul
>
>
>
>
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
