Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.arch.embedded
Subject: Re: Embedded Linux: share data among different processes
Date: Fri, 24 Jun 2016 13:52:07 -0700
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <87fus2qphk.fsf@nightsong.com>
References: <nkgihf$dn7$1@dont-email.me> <87r3bnr9as.fsf@nightsong.com> <nkj6c2$oer$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="52eac348160ce62b68e4635eee7cc854"; logging-data="11952"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/NR9pfKMQ77oiXWV+ZkXp2"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:LNgCBxdDwcQS4DFYK/xU9RkfcXQ= sha1:5jBmONm6fHuaESMzGIo0SkghEpg=
Xref: csiph.com comp.arch.embedded:24340

pozz <pozzugno@gmail.com> writes:
> The status data that changes frequently will be maximum 100-200 bytes
> (I think it will be less than 100 bytes).

If "frequently" means less than a few times per second and you have
enough hardware resources, you'll probably have an easier time writing
this as if it were a desktop or web app than using a traditional
embedded approach.  That can even including writing the host part in a
server-side scripting language instead of something like C.