Re: Suggestions for custom application-layer protocol?

From: Dave (root_at_localhost.com)
Date: 05/26/05

  • Next message: Glyn Davies: "Re: Suggestions for custom application-layer protocol?" 
    Date: Thu, 26 May 2005 13:11:22 +0800

    Sean Burke wrote:

    > "Mark" <mark_2811nospam@excite.com> writes:
    >
    >
    >>I need to implement a simple application layer protocol that will be used to
    >>communicate between an embedded device (single-board computer running Linux)
    >>and a monitoring terminal (running Windows). There isn't alot of data being
    >>passed around, mostly status information collected by the embedded device,
    >>and control messages from the monitoring terminal. Messages will consist of
    >>between 1 and 10 fields of data.
    >>
    >>I want the protocol to be text based rather than binary since the data
    >>throughput is low. I also want the protocol to be based on TCP/IP. Does
    >>anyone here have any suggestions on the design of a simple protocol? Are
    >>there simple, standard ways of formatting text messages to be sent over a
    >>TCP socket (such as comma-separated)? I would prefer to avoid the
    >>complexities of XML. Since either the embedded device or the monitoring
    >>terminal can initiate a message, is it preferable to have TCP servers
    >>running on both sides? Or is it better to simply leave a TCP connection
    >>open between client and server? Any suggestions on ultra-simple standard
    >>protocols that do something similar to this?
    >>
    >>Any suggestions or pointers to further reading are much appreciated.
    >
    >
    > One option to consider is to embed a web interface into your
    > application. This has the advantage that you can use any web
    > browser as the client side of the interface.
    >
    > There are a variety of very small web servers that are suitable
    > for embedding. One such that I have used successfully is "pserv".
    > From the FreeBSD ports description:
    >
    > | pServ is a small, portable HTTP server. It is written in pure C for speed and
    > | portability. It runs as a standalone program and does not require inetd.
    > | It should be small enough to be used in a mobile computer or to be run on your
    > | obsolete workstation you have somewhere.
    > |
    > | This port contains a patched version to support the execution of php scripts.
    > |
    > | WWW: http://sourceforge.net/projects/pserv/
    >
    I don't think this link is even exist.

    D

    > -SEan
    >
    >

  • Next message: Glyn Davies: "Re: Suggestions for custom application-layer protocol?"

    Relevant Pages

    • Re: Suggestions for custom application-layer protocol?
      ... >>I need to implement a simple application layer protocol that will be used to ... >>and a monitoring terminal (running Windows). ... is it preferable to have TCP servers ... > | pServ is a small, portable HTTP server. ...
      (comp.unix.programmer)
    • Re: SBS 2003 - Remote Connection Manager
      ... The Client is running Windows XP SP2, in terms of protocol - the client is ... >> Hi Marina, ...
      (microsoft.public.windows.server.sbs)
    • Re: Desktop <-> Web
      ... There are APIs on the client side which are higher level than Net::HTTP. ... AMQP protocol - various servers inc RabbitMQ ... Stomp protocol over HTTP - various servers inc Apache ActiveMQ ... Another option is to use XMPP as the transport. ...
      (comp.lang.ruby)
    • Re: [9fans] (no subject)
      ... and see if there exists somehost on protocol $protocol for service 9fs. ... the current algorithm doesn't check to see if any servers were found. ... the first version in sourcesdump also has the break. ...
      (comp.os.plan9)
    • Re: POHMELFS high performance network filesystem. Transactions, failover, performance.
      ... relatively slow links, especially with multiple servers. ... Also, efficiently recovering from a link/server failure, when clients ... synchronising protocol between recovering servers. ... features as long as switching to different servers in case of failure. ...
      (Linux-Kernel)