Comments on: JeeMon as web server http://jeelabs.org/2010/03/02/jeemon-as-web-server/ Computing stuff tied to the physical world Tue, 22 May 2012 20:33:35 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: jcw http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1190 jcw Tue, 09 Mar 2010 20:58:48 +0000 http://news.jeelabs.org/?p=6209#comment-1190 <p>Heh, thx! :)</p> Heh, thx! :)

]]> By: jonS http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1189 jonS Tue, 09 Mar 2010 20:25:01 +0000 http://news.jeelabs.org/?p=6209#comment-1189 <p>Just driving by -- JC, this stuff is awesome. Your ideas are so on target for this new world of sensors connected everywhere. I just found your site and the combination of low-power radio + cheap nodes is, well, awesome! Thanks for working on this project for us all.</p> Just driving by — JC, this stuff is awesome. Your ideas are so on target for this new world of sensors connected everywhere. I just found your site and the combination of low-power radio + cheap nodes is, well, awesome! Thanks for working on this project for us all.

]]> By: tamberg http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1169 tamberg Wed, 03 Mar 2010 11:36:51 +0000 http://news.jeelabs.org/?p=6209#comment-1169 <p>@jcw: To hook up to Yaler your embedded server will have to turn into a HTTP client until the Reverse HTTP connection is established. Reversing usually requires access to the socket of your outgoing HTTP connection. After this initial handshake everything remains as it is now, as long as you serve relative URIs only. Otherwise you'll have to rewrite the host part of the URI, eg. http://device-IP/my.html becomes http://yaler.net/device-ID/my.html . That's it.</p> @jcw: To hook up to Yaler your embedded server will have to turn into a HTTP client until the Reverse HTTP connection is established. Reversing usually requires access to the socket of your outgoing HTTP connection. After this initial handshake everything remains as it is now, as long as you serve relative URIs only. Otherwise you’ll have to rewrite the host part of the URI, eg. http://device-IP/my.html becomes http://yaler.net/device-ID/my.html . That’s it.

]]> By: jcw http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1165 jcw Tue, 02 Mar 2010 11:06:37 +0000 http://news.jeelabs.org/?p=6209#comment-1165 <p>Yaler looks inteRESTing ;) - what would it take to hook up to it? I'm still having some trouble wrapping my head around how it will work in practice - but I'mm sure that'll improve soon enough. Look also at tomorrow's post for some "push" processing.</p> Yaler looks inteRESTing ;) – what would it take to hook up to it? I’m still having some trouble wrapping my head around how it will work in practice – but I’mm sure that’ll improve soon enough. Look also at tomorrow’s post for some “push” processing.

]]> By: jcw http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1164 jcw Tue, 02 Mar 2010 11:04:02 +0000 http://news.jeelabs.org/?p=6209#comment-1164 <p>The plan is indeed to abstract away from any particular DB interface. It's a bit more work, I haven't figured it all out yet...</p> <p>Glad to hear you like the weblog!!!</p> The plan is indeed to abstract away from any particular DB interface. It’s a bit more work, I haven’t figured it all out yet…

Glad to hear you like the weblog!!!

]]> By: tamberg http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1163 tamberg Tue, 02 Mar 2010 01:02:48 +0000 http://news.jeelabs.org/?p=6209#comment-1163 <p>Hi Jean-Claude,</p> <p>very interesting work!</p> <p>Because as you say "on tiny embedded Linux systems, an HTTP server will probably be the only option to present information." you might be interested in making such an embedded server accessible to any browser without having to worry about public IPs, NATs or firewall settings.</p> <p>We are currently developing Yaler, a simple, RESTful, open source relay infrastructure solving exactly this problem. Please visit http://yaler.org/ for more information on the project.</p> <p>Kind regards, Thomas</p> Hi Jean-Claude,

very interesting work!

Because as you say “on tiny embedded Linux systems, an HTTP server will probably be the only option to present information.” you might be interested in making such an embedded server accessible to any browser without having to worry about public IPs, NATs or firewall settings.

We are currently developing Yaler, a simple, RESTful, open source relay infrastructure solving exactly this problem. Please visit http://yaler.org/ for more information on the project.

Kind regards, Thomas

]]> By: Marius Kintel http://jeelabs.org/2010/03/02/jeemon-as-web-server/#comment-1162 Marius Kintel Tue, 02 Mar 2010 00:16:11 +0000 http://news.jeelabs.org/?p=6209#comment-1162 <p>It looks like metakit is around the corner :)</p> <p>Whenever you get to that, just a small request: For us who are not familiar with metakit, it would be cool with a little blurb about how metakit differs from typical other databases which could be used for this purpose (sqlite, berkeley db or even postgresql). ..or maybe even abstract away the database interfaces in JeeMon to make it trivial to choose smth. familiar as a backend, which could be useful if one is to integrate data collected from jeenodes into larger or existing systems.</p> <p>I really enjoy your blogposts describing the jeemon system while it's being designed/evolved. Keep up the good work!</p> It looks like metakit is around the corner :)

Whenever you get to that, just a small request: For us who are not familiar with metakit, it would be cool with a little blurb about how metakit differs from typical other databases which could be used for this purpose (sqlite, berkeley db or even postgresql). ..or maybe even abstract away the database interfaces in JeeMon to make it trivial to choose smth. familiar as a backend, which could be useful if one is to integrate data collected from jeenodes into larger or existing systems.

I really enjoy your blogposts describing the jeemon system while it’s being designed/evolved. Keep up the good work!

]]>