<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Andreas.<br>
<br>
On 2014-12-18 21:42 , Andreas Götz wrote:<br>
</div>
<blockquote
cite="mid:A8AF53AA-024A-42B3-B784-928D5503AA43@gmail.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div><br>
<blockquote type="cite">vzlogger would <i>always</i> throw an
error, either<br>
<blockquote type="cite">CURL: Couldn't resolve host name</blockquote>
or<br>
<blockquote type="cite">CURL: URL using bad/illegal format or
missing URL</blockquote>
It would not quit, though, so in the end it did what I wanted
(not push the readings to the middleware), but it's not a
clean solution.<br>
</blockquote>
You need to change the api, not the middleware. Middleware is a
feature of the vz api. Never tried though.<br>
<br>
</div>
</blockquote>
Sorry, I don't get your point, maybe I'm slow? Why change the API or
the middleware? Would that not simply be a change in vzlogger
behavior independent on how the API or the middleware looks
like/works?<br>
<br>
My idea was to tell the vzlogger daemon <i>not</i> to send the
meter readings anywhere, just to collect them. I would then query
vzlogger via the internal microhttpd for the current readings...<br>
<br>
KR,<br>
<br>
Ralf<br>
<br>
</body>
</html>