[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] CoapServer and duplicate EndPoints
|
Hi Kiran
I not sure if this is a good solution, nor if we want this...
Why would someone add two conflicting endpoints? (I think this should be checked by the application logic.)
How does it help when there is an error just a bit earlier?
Maybe someone wants to add coordinated endpoints using the same address while control their start/stop lifecycle?
How would this work for alternative transports like SMS?
Ciao
Matthias
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kiran Pradeep
> Sent: Sonntag, 18. Oktober 2015 08:37
> To: cf-dev@xxxxxxxxxxx
> Subject: [cf-dev] CoapServer and duplicate EndPoints
>
> Hi,
> Currently CoapServer.java stores EndPoints as an ArrayList<EndPoint>.
> This doesn't prevent user from adding same EndPoint twice. Could it be like
> Map<InetSocketAddress,EndPoint> ?
>
> For e.g. Leshan's SecurityIntegrationTestHelper::createPSKClient()
> will end up adding same EndPoint with and without DTLS.
>
> Thanks,
> Kiran.
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev
