From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.25.208.212 with SMTP id h203csp1544080lfg; Thu, 5 Feb 2015 18:19:00 -0800 (PST) X-Received: by 10.224.75.71 with SMTP id x7mr3094153qaj.90.1423189139978; Thu, 05 Feb 2015 18:18:59 -0800 (PST) Return-Path: Received: from mail-yk0-x240.google.com (mail-yk0-x240.google.com. [2607:f8b0:4002:c07::240]) by mx.google.com with ESMTPS id 49si72824qgb.16.2015.02.05.18.18.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 18:18:59 -0800 (PST) Received-SPF: pass (google.com: domain of rack-devel+bncBDQJJMFBWYFBBEGJ2CTAKGQEBJIRS4Y@googlegroups.com designates 2607:f8b0:4002:c07::240 as permitted sender) client-ip=2607:f8b0:4002:c07::240; Authentication-Results: mx.google.com; spf=pass (google.com: domain of rack-devel+bncBDQJJMFBWYFBBEGJ2CTAKGQEBJIRS4Y@googlegroups.com designates 2607:f8b0:4002:c07::240 as permitted sender) smtp.mail=rack-devel+bncBDQJJMFBWYFBBEGJ2CTAKGQEBJIRS4Y@googlegroups.com; dkim=pass header.i=@googlegroups.com Received: by mail-yk0-x240.google.com with SMTP id 79sf627096ykr.9; Thu, 05 Feb 2015 18:18:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:subject:mime-version:content-type :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; bh=Zj5UpxkiCjuuWB6WWcNr6708f2wNEFnpeGTvOrZu0Gc=; b=IJ0UeYi/mHjhOFAkque33nz+3SIUX+1OR9W4nKxHNp9no5T2+fEmoK03bcnktiH6+S eEdbNBNsJpu9LV5vS+IIOQ8JEdVSmrkqtTf7BkxJ015r5QMoiYGyzcKoECTyYwgEdjxL Ghpe8ZxmMHlmfDhKzgbsuQKEvNXOOLt5nf4sNPX1SZus6oje2Dh1diyF3BmJv4UoDQlT MA/8lGMJ+Tluq/kCMiR0YNT4OaxV8bA5cZ2oaUE9QbvZzJiNKQViyeUxO52uQvweqDlw PfPxbbh2ONO2y4/oOa05Bothh2wQmphZmmC3yMePlJTUcB7d67bpeVVhF9tzeLbHYh4j jsqw== X-Received: by 10.182.76.2 with SMTP id g2mr7107obw.8.1423189137108; Thu, 05 Feb 2015 18:18:57 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.182.22.231 with SMTP id h7ls348326obf.87.gmail; Thu, 05 Feb 2015 18:18:56 -0800 (PST) X-Received: by 10.182.104.37 with SMTP id gb5mr1225041obb.45.1423189136446; Thu, 05 Feb 2015 18:18:56 -0800 (PST) Received: by 10.224.86.71 with SMTP id r7msqal; Thu, 5 Feb 2015 07:15:55 -0800 (PST) X-Received: by 10.140.40.242 with SMTP id x105mr57429qgx.14.1423149355317; Thu, 05 Feb 2015 07:15:55 -0800 (PST) Date: Thu, 5 Feb 2015 07:15:54 -0800 (PST) From: spam@orgizm.net To: rack-devel@googlegroups.com Message-Id: <210092bd-3fac-47e9-8dd4-66707e414e8e@googlegroups.com> Subject: CoAP server with Rack interface MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_5826_1960765658.1423149354898" X-Original-Sender: spam@orgizm.net Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , ------=_Part_5826_1960765658.1423149354898 Content-Type: multipart/alternative; boundary="----=_Part_5827_1451850791.1423149354898" ------=_Part_5827_1451850791.1423149354898 Content-Type: text/plain; charset=UTF-8 Hey, I'm working on a CoAP [0] server with a Rack interface for my diploma thesis: https://github.com/nning/david Your feedback would be very valuable for me although it is not clear, I manage to make many changes based on it before handing in the thesis. I compiled a quick README and hope it suffices as a starting point for testing the server. Maybe it is just interesting, the Rack interface is used in another protocol context. Some more info on CoAP from RFC7252: The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. Thanks! henning [0] https://tools.ietf.org/html/rfc7252 -- --- You received this message because you are subscribed to the Google Groups "Rack Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_5827_1451850791.1423149354898 Content-Type: text/html; charset=UTF-8 
Hey,

I'm working on a CoAP [0] server with a Rack interface for my diploma
thesis:

https://github.com/nning/david

Your feedback would be very valuable for me although it is not clear, I
manage to make many changes based on it before handing in the thesis. I
compiled a quick README and hope it suffices as a starting point for
testing the server. Maybe it is just interesting, the Rack interface is
used in another protocol context.

Some more info on CoAP from RFC7252:

The Constrained Application Protocol (CoAP) is a specialized web
transfer protocol for use with constrained nodes and constrained
(e.g., low-power, lossy) networks. The protocol is designed for machine-
to-machine (M2M) applications such as smart energy and building
automation.

CoAP provides a request/response interaction model between
application endpoints, supports built-in discovery of services and
resources, and includes key concepts of the Web such as URIs and
Internet media types. CoAP is designed to easily interface with HTTP
for integration with the Web while meeting specialized requirements
such as multicast support, very low overhead, and simplicity for
constrained environments.

Thanks!
henning

[0] https://tools.ietf.org/html/rfc7252

--

---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
------=_Part_5827_1451850791.1423149354898-- ------=_Part_5826_1960765658.1423149354898--