Re: Suggestions for custom application-layer protocol?

From: James Antill (james-netnews_at_and.org)
Date: 05/27/05

  • Next message: James Antill: "Re: Suggestions for custom application-layer protocol?" 
    Date: Fri, 27 May 2005 01:04:17 -0400

    On Wed, 25 May 2005 19:21:02 +0000, Sean Burke wrote:

    > 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.

     Not a terrible idea, a simple HTTP/1.0 server can be pretty small esp. if
    you don't mind stopping as soon as something works (the very basics can be
    done in < 20 lines of C).

    > 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:

     Yeh, pretty good ... I stopped looking after seeing 2 major
    vulnerabilities on the first google page.
     The code also looked promising ... for more exploits.

     Writing a custom "simple protocol" is likely to be much easier, using
    netstrings is probably more likely to make you do the right thing ... but
    a simple "CMD arg1 arg2" type telnet/SMTP/NNTP like protocol isn't hard to
    get right. 

    -- 
James Antill -- james@and.org
http://www.and.org/vstr/httpd
  • Next message: James Antill: "Re: Suggestions for custom application-layer protocol?"

    Relevant Pages

    • RE: [slightly OT] Web Applications
      ... Whenever you go into a discussion with a client you will always loose it. ... > applications via the internet. ... > client, which is a VFP-built user interface, and not a browser ...
      (microsoft.public.fox.helpwanted)
    • Re: Suggestions for custom application-layer protocol?
      ... > browser as the client side of the interface. ... The code also looked promising ... ...
      (comp.unix.programmer)
    • Re: [slightly OT] Web Applications
      ... > applications via the internet. ... > client, which is a VFP-built user interface, and not a browser ...
      (microsoft.public.fox.helpwanted)
    • Re: What doesnt lend itself to OO?
      ... >>server is a pure data transfer interface. ... essentially exposing the client or service implementation. ... >>paradigms can be abstracted just like any other problem space in an OO ...
      (comp.object)
    • Re: Text terminal rendering design
      ... free to give it any object that satisfies that interface. ... giving it a real facade object if I choose. ... Facade to avoid touching the client. ... completely incompatible with this subsystem interface. ...
      (comp.object)