rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: spam@orgizm.net
To: rack-devel@googlegroups.com
Subject: CoAP server with Rack interface
Date: Thu, 5 Feb 2015 07:15:54 -0800 (PST)	[thread overview]
Message-ID: <210092bd-3fac-47e9-8dd4-66707e414e8e@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1528 bytes --]



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.

[-- Attachment #1.2: Type: text/html, Size: 1888 bytes --]

                 reply	other threads:[~2015-02-06  2:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=210092bd-3fac-47e9-8dd4-66707e414e8e@googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).