unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Look for data serialisation format to implement communication between Emacs and external program.
Date: Sun, 06 Jan 2013 23:44:46 +0200	[thread overview]
Message-ID: <87ehhyc7g1.fsf@gavenkoa.example.com> (raw)

I know that XML is BAD so avoid it.

My experience with 'expect' show me that simple string data communication is
good but some times data have same pattern as _prompt_ so I can't distinct
control data from regular data.

Prefixes like in 'diff' file format resolve this issue. But this move us to
TLV (table-length-value) format.

Standard TLV format described by ASN.1 BER coding schema.

Is that right to use ASN.1 BER as serialisation data format for communication
between Emacs and external program?

My external application is not jet written but I select Python as
implementation language. Seems 'python-pyasn1' library make work from Python
side:

  http://pyasn1.sourceforge.net/

How about Emacs? Is there any library for creating/parsing ASN.1 BER data?

I need only basic types, like structure of numbers and UTF-8 strings (blogging
software - pass command and data like article + title + list of tags)...

Another formats like JSON or sexp also look nice but I don't know about Emacs
support for this formats.

I didn't look yet to projects like pymacs, which solved such task.

Any advice is welcome!

-- 
Best regards!




             reply	other threads:[~2013-01-06 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 21:44 Oleksandr Gavenko [this message]
2013-01-06 22:46 ` Look for data serialisation format to implement communication between Emacs and external program Thien-Thi Nguyen
2013-01-07 13:35   ` Oleksandr Gavenko
2013-01-08  9:44     ` Thien-Thi Nguyen
2013-01-07 21:57   ` Oleksandr Gavenko
     [not found] <mailman.16821.1357508702.855.help-gnu-emacs@gnu.org>
2013-01-07  7:53 ` Helmut Eller
2013-01-07 13:53   ` Oleksandr Gavenko

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-all from there: mbox

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87ehhyc7g1.fsf@gavenkoa.example.com \
    --to=gavenkoa@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).