Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kura-dev] CoAP support in Kura through Eclipse Californium

Thanks Buddhika,

I'll take a look tomorrow.


In the meantime we should start with the GSoC CoAP project.


We could start with a simple scenario we use in some of our examples in Kura.

Take a look to the org.eclipse.kura.example.publisher.


This bundle publishes an MQTT message periodically to the broker.


Please study the code and the path of the message through the CloudService, DataService, DataTransportService and finally the Eclipse MQTT Paho client.


Ideally we would like to provide the same service over CoAP (Eclipse Californium) without breaking (too much) the CloudService and DataService APIs (which are quite MQTT-centric).


The DataTransportService was designed to slightly abstract the underlying protocol.

The MqttDataTransport is an implementation for MQTT (using the Paho library).


For this project we would like to implement a CoapDataTransport providing an alternate "telemetry transport" over Californium.


Please study the above example and make a proposal on how we could try to achieve this new implementation.

For the moment just focus on the periodical sending of a message.


Ciao,

Cristiano

Da: kura-dev-bounces@xxxxxxxxxxx <kura-dev-bounces@xxxxxxxxxxx> per conto di Buddhika Dilhan <buddhika.dilhan5@xxxxxxxxx>
Inviato: domenica 22 giugno 2014 03.33
A: Kura Developers mailing list
Oggetto: Re: [kura-dev] CoAP support in Kura through Eclipse Californium
 
Hi Cristiano,

I think this is the patch. :) 

thanks.

Buddhika Dilhan
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.


On Wed, Jun 18, 2014 at 7:41 PM, Cristiano De Alti <cristiano.dealti@xxxxxxxxxxxx> wrote:
Hi Buddhika,
   There must be something wrong. If you changed only a few lines that patch must be very small.
If I've understood correclty you only changed two pom files, right?

Try the following:

1. Clone a fresh Kura repository
2. Make the changes you want to submit as a patch
3. issue 'git diff' to see the differences between the working copy and the head. They should be limited to the files you changed (they can be read in the diff output).
3. commit your changes (git commit -a -m "Fixed...")
4. issue 'git log' and find the SHA of your commit e.g: 27abf1f59ee0bb852ee49042ead4b324fc659e46
5. Format the patch again with git format-patch -1 27abf1f59ee0bb852ee49042ead4b324fc659e46
    It's content should be similar to the output of git diff of step 3

Otherwise, just send me the files you have changed.

Ciao,
  Cristiano



On 18/06/2014 15:29, Buddhika Dilhan wrote:
Hi Christiano,
I cleaned the repo and created the patch in the command line. but the patch was same size as it before. so I created the patch using eclipse IDE that weighted 1.1 MB. 
when I try to send it, it gave an error saying that git patch contains a line longer than 998 characters solution
I used --no-validate command and sent the e mail to the mailing list by using smtp.gmail server.
I hope its ok. 

thanks

Buddhika Dilhan
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.


On Wed, Jun 18, 2014 at 11:44 AM, De Alti, Cristiano <Cristiano.DeAlti@xxxxxxxxxxxx> wrote:

Hi Buddhika,

There is something wrong with your second patch (0002): it's 15MB in size.

It looks too much for a few lines patch.


Please recreate the patches starting from a clean kura repository.


Your patch should only contain hunks for the file you changed.


Patches are usually sent to mailing lists using git-send-email:

http://git-scm.com/docs/git-send-email


This is a workflow I used in the past (to the barebox ML). Study it and adapt it to your needs:


git format-patch --to barebox@xxxxxxxxxxxxxxxxxxx -1 a273740577f2ba370d6ff7e213b9c9724637f105

Send patches to the ML:

git send-email --smtp-server=smtp.live.com --smtp-server-port=587 --smtp-encryption=tls --smtp-user=<your username> --smtp-pass=<your password> 0001-cfi_flash.c-correct-calculation-of-region-erasesize-.patch

Make sure the patch is signed-off by you

Thanks,

Cristiano

Da: kura-dev-bounces@xxxxxxxxxxx <kura-dev-bounces@xxxxxxxxxxx> per conto di Buddhika Dilhan <buddhika.dilhan5@xxxxxxxxx>
Inviato: mercoledì 18 giugno 2014 04.17
A: Kura Developers mailing list
Oggetto: Re: [kura-dev] CoAP support in Kura through Eclipse Californium
 
hi, 
my message is being held as it is too big. it is waiting for moderators approval.
is there any thing I can do for it??
thanks

Buddhika Dilhan
Undergraduate,
Department of Computer Science and Engineering,
University of Moratuwa.




_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/kura-dev




_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/kura-dev

--
Cristiano De Alti
Principal Software Engineer

direct:    +39 0433 485468

EUROTECH
Imagine.Build.Succeed.
HEADQUARTERS
EUROTECH S.p.A. – Via Fratelli Solari, 3/a | 33020 Amaro UD | Italy | Tel. +39. 0433 485411  | Fax +39. 0433 485499 |
Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine 196115
www.eurotech.com
____________________________________

Il presente messaggio ed ogni suo allegato sono da intendersi inviati esclusivamente agli effettivi destinatari e potrebbero essere soggetti a restrizioni legali. Se avete ricevuto questo messaggio per errore vi invitiamo a darne immediata notifica al mittente e cancellarlo dal vostro sistema. Qualsiasi altro uso di questo messaggio da parte vostra e' strettamente proibito.
 
This e-mail, and any file attached to it, is meant only for the intended recipient of the transmission and may be a communication privileged by law. If you have received it in error, please notify the sender immediately and delete the original from your system. Any other use of this e-mail by you is strictly forbidden.
____________________________________
 
Per favore, pensate all’ambiente prima di stampare questa e-mail. Please consider the environment before printing this e-mail.

_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/kura-dev


Back to the top