cieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
<http://ext.samsung.net/mailcheck/SeenTimeChecker?do=c03cb6296d7f11883cad70b
e01dbbc61464dba7d5850bc6a6644ab31040311a5be7dd83ce6b932973c40f787d33f357d4b3
1597edd603a7ce5a22f09e2218feaa728c55b39cc59eacf878f9a26ce15a0>
-- next part
Hi Thiago,
BT on RFComm and BLE-GATT have been implemented on the IoTivity with the
concept of connectivity extension which planned to align to OIC spec.
6lo-over-BTLE can resolve the problem by giving us IPv6. But we need to wait
more than 5 year I expect for common use.
Not only for BT/BLE bu
org/pipermail/iotivity-dev/attachments/20160211/34223632/attachment.html>
p://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/bd20e16a/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111957921_Z5JE7EUA.gif
Type: image/gif
Size: 13168 bytes
Desc: 201602111957921_Z5JE7EUA.gif
URL:
<http://li
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/385eab9d/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111957921_Z5JE7EUA.gif
Type: image/gif
Size: 13168 bytes
Des
Hi Raghavendra Kakarla,
>
> From: iotivity-dev-bounces at lists.iotivity.org lists.iotivity.org> on behalf of Raghavendra Kakarla inedasystems.com>
> Sent: Monday, February 8, 2016 10:33 PM
> To: Thiago Macieira
> Cc: iotivity-dev at lists.iotivity.org
>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/d906e93e/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602112152178_BEI0XT4N.gif
Type: image/gif
Size: 13168 bytes
Des
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/59ebef12/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: Proposal_MultiAppSupport.pdf
Type: application/octet-stream
Size: 155475
oic-presence
<https://github.com/otcshare/iotivity-node/blob/master/spec/iot-js-spec.md>
namely, the optional 'USVString url' parameter to 'subscribe()' and
'unsubscribe()' would become an explicit
'USVString deviceId'.
Best regards,
Zoltan
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/b6d3b9e4/attachment.html>
https://wiki.iotivity.org/community
- Accessing Web Services from IoT Devices from Ziran Sun
- Connected Tizen from myself
Regards
--
https://wiki.tizen.org/wiki/User:Pcoval
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/b82d1da7/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111729403_BEI0XT4N.gif
Type: image/gif
Size: 13168 byte
On quinta-feira, 11 de fevereiro de 2016 11:14:41 PST Kis, Zoltan wrote:
> Sorry for noticing this late. IIRC the URL property was meant to have the IP
> address and port, if that would be of interest to JS clients. I agree that
> a single 'url' property is less clear than using an explicit 'addres
On quinta-feira, 11 de fevereiro de 2016 12:52:46 PST ??? wrote:
> Hi Thiago,
>
>
> >>Do we need BT? No, seriously, is it required? Can we not require a socket
> >>interface, like IPv4 and IPv6?
> I think the majority of smartphones and smartwatches on the maket today do
> include BT/BLE support
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160211/7e837385/attachment.html>
14 matches
Mail list logo