hi. two things. first, where/what is "Alex's draft"?
second, do you want me to submit a draft talking about syslog with reliable
delivery using beep?
thanks,
/mtr
Hi Folks,
Just wanted to pass this along.
Documentation, source code, sample code, bug repository and more can be found
at the RoadRunner project site:
http://rr.codefactory.se/
and the coolest part, you can buy T-shirts!
/mtr
I was using fleXML to generate a parser for the syslog COOKED DTD and
ran across a little ommission. The entity %ATEXT used to define some of
the attributes seems to be missing. Is this an omission or am just
missing something (I'm not very familiar with DTDs).
hi. you're right.
darren -
well, as the resident beep guy, i guess i get to comment. however,
rather than answer your questions directly, i'm going to state a general
principle and then let you apply it to your situation.
the principle is this:
there is nothing stopping anyone from writing their own limited beep
in fact, the just say no thing works great for most of
beep's features. what you're left with is a mandatory framing
mechanism and some xml parsing for channel 0.
Well, I thought this was not the spirit of BEEP - but I guess you must
know better ;) I'll re-read the RFC in this regard.
At 01:48 PM 12/18/2002 -0800, Darren New wrote:
Bennett Todd wrote:
Yes indeedy and then some. Multiplexed streams of
MIME-structure-framed XML seems a bit over the top, no?
Um BEEP uses SSL. BEEP includes a mechanism for saying you want to
use SSL. (Well, TLS, but you know that.)
Marshall Rose wrote:
| this message is longer than i'd like, for which i apologize in advance.
|
| [...]
|
| one of the values behind standardization, and in particular,
| standardization of open protocols is that you get a concensus behind
| something [...]
One thing about which
We're meeting this afternoon and I've been remiss in asking for volunteers
to act as Scibe and to do the text conferencing. Are there any
volunteers?
i'm planning on attending, so i'll volunteer for both.
/mtr
The difference is in this line:
C: lt;166gt; 1990 Oct 22 01:00:00 bomb tick[0]:
BOOM!/entry
I think the needs to be escaped to gt; - am I right?
i don't think so... the only things that you must escape in XML are and .
isn't special when it occurs in #pcdata.
/mtr
I think the cleanest approach is to put the transport into a separate
RFC and publish the UDP mapping concurrently with -protocol. However,
considering that the whole transport description for UDP is just use
port 514, I am not sure if the WG wants to go with the overhead of
extra RFC
10 matches
Mail list logo
