IOT October 2015

iot@xmpp.org

5 participants
5 discussions

by Peter Waher

Hello During the work in other standards groups, there has been some interest in the discovery model presented in XEP-0347. This has lead to the desire to update the IoT-discovery encoding described in the XEP somewhat and formalize it into a URI scheme. I've therefore prepared an application to IANA for a provisional URI scheme. The idea is to send it by the end of next week. So, if you have time, and an interest, you're welcome to return any comments, suggestions or questions to me by then, so I have a chance to update the application before mailing it. The idea is to update XEP-0347 after the approval of such a provisional URI scheme. Best regards, Peter Waher

10 years, 9 months

COAP as Streaming Source

by Sadaf Khan

Hi i am working on coap protocol for an Iot Application .I' ve made this as a Spark-Streaming Source. i simply 've made a resource and add it to my server as a observable resource. then i start observing it through myclient, It fetches the data perfectly but also gives the following exception. 15/10/14 13:49:48 ERROR BlockGenerator: Error in block pushing thread java.io.NotSerializableException: org.eclipse.californium.core.CoapObserveRelation Serialization stack: - object not serializable (class: org.eclipse.californium.core.CoapObserveRelation, value: org.eclipse.californium.core.CoapObserveRelation@25d5cb65) at org.apache.spark.serializer.SerializationDebugger$.improveException(SerializationDebugger.scala:40) at org.apache.spark.serializer.JavaSerializationStream.writeObject(JavaSerializer.scala:47) at org.apache.spark.serializer.SerializationStream.writeAll(Serializer.scala:153) at org.apache.spark.storage.BlockManager.dataSerializeStream(BlockManager.scala:1189) at org.apache.spark.storage.BlockManager.dataSerialize(BlockManager.scala:1198) at org.apache.spark.storage.BlockManager.doPut(BlockManager.scala:850) at org.apache.spark.storage.BlockManager.putIterator(BlockManager.scala:637) at org.apache.spark.streaming.receiver.BlockManagerBasedBlockHandler.storeBlock(ReceivedBlockHandler.scala:77) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl.pushAndReportBlock(ReceiverSupervisorImpl.scala:141) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl.pushArrayBuffer(ReceiverSupervisorImpl.scala:112) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl$$anon$2.onPushBlock(ReceiverSupervisorImpl.scala:97) at org.apache.spark.streaming.receiver.BlockGenerator.pushBlock(BlockGenerator.scala:198) at org.apache.spark.streaming.receiver.BlockGenerator.org $apache$spark$streaming$receiver$BlockGenerator$$keepPushingBlocks(BlockGenerator.scala:171) at org.apache.spark.streaming.receiver.BlockGenerator$$anon$1.run(BlockGenerator.scala:89) can anyone have idea about this.? This is my custom receiver for making my client to stream it. class customReceiver(test:String) extends Receiver[CoapObserveRelation](StorageLevel.MEMORY_AND_DISK_2) with Logging{ @volatile private var stopped = false override def onStart() { val client = new CoapClient("coap://localhost/temp") var response=client.observe(new CoapHandler() { override def onLoad(response: CoapResponse) { } override def onError() { System.err.println("Failed") } }) response.proactiveCancel(); store(response) } } Any help is much awaited and appreciated :) Thanks

10 years, 10 months

Re: [IOT] [Standards] Blocking messages from unsubscribed users

by Joachim Lindborg

In the case of IoT i use it a lot devices only look at subscription requests from unsubscribe do users. And I also have component that takes care of devices blocking all messages from non subscribed Don't know if I need a xep for it or if its implementation specific for IoT I would like to be able to turn it on as default for myself receiving only subscription requests just as I have setup Skype måndag 12 oktober 2015 skrev Steffen Larsen <zooldk(a)gmail.com>: > Hi Matthew, > > Good call. The scenario I have used blocked commands was in a setup where > I actually needed configuration instead (setup once). > So for me and the scenarios I have, the ad-hoc command config would be > great!. > > The only problem I see, is that every server would vary a lot.. and have > different policies. > > /Steffen > > On 12 Oct 2015, at 23:28, Matthew Wild <mwild1(a)gmail.com <javascript:;>> > wrote: > > > > It seems a few people are requesting this. I'd like to understand the > use-cases. > > > > For example, if this is something you want to be the default > > behaviour, isn't it better as a deployment configuration? No protocol > > needed. > > > > A per-user configuration would also be possible using ad-hoc commands. > > Again, no extra XEPs needed. > > > > Just throwing things out there, I'd like to understand exactly what > people want. > > > > Regards, > > Matthew > > -- *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg(a)sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270

10 years, 10 months

How to make Coap as Streaming Source

by Sadaf Khan

Hi, I am working on COAP-IOT protocol. i want to embed it as a streaming source in my application. Is it possible to do this via spark streaming. ?? Thanks in anticipation.

10 years, 10 months

XMPP protocol.

by Sadaf Khan

Hi, I am doing R&D on xmpp protocol. I need its iot extensions protocol. i.e XEP-0323 and XEP-0325.But i just found one example of its applicaiton in xml. can you suggest its JAVA library? i will be very thankful to you.)

10 years, 10 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

IOT October 2015