On 16 Jan 2003 15:02:23 +0100 Moritz Angermann <[EMAIL PROTECTED]>
babbled:
> This Network thingy is something really attracting me.
> if i understand it right, that doesn't include a protocol lib, right?
> i mean i'd LOVE to have some netowrk-evas like thingy *g* haha.
i see you're seeing my evil plan all coming together then eh? :) yes - this
woudl be the reason for 1. a generic fd loop system and the idea of adding in an
ipc wrapper.
> thoug my c isn't that good ( i keep improving, reading books...
> practacing... ).
> so would it be any use of a 'e-protocol-lib' ? based on your
> network code?
well the way i had it planned - you wouldn't need one. ecore would do the nuts
and bolts of connect/authenticate and encrypt (if desired, but to start i'd just
do local unix socket where we don't need to do any of these things, just
send/receive data), and it would handle buffering and splitting the data stream
into packets of data and then be able to take these data lumps from the sender
and then decode them for the receiver - the receiver now needs to figure out
what these data lumps really mean - and this will literally be on a per-protocol
basis (but now the hard work is done anyway). This is one of the big reasons eet
can encode/decode data structures to arbitrary chunks of memory... it can be a
protocol generator/decoder... and the client or server literally send data
structs to each other... how convenient! :) now the client can easily say "send
this struct..." or "send this data lump..." and the other end can say "read this
data struct.." or "read this data lump" i think there isn't much more than can
be done... except lots of example code :)
the most i was envisaging ecore doing would be able to safely break up and
buffer the data stream into chunks that have the following info:
DWORD Ecore mssage magic number header
DWORD Message type
DWORD Data payload size
....data payload data...
ecore would safely check that the magic number is there (to check for
corruption), take out the message type and present that nicely in an api to the
program and then copy out the data payload and return its size (with checking
consistency etc.) and now the app can (depending on the message type) decode the
payload as it pleases (be it a string, data struct, image data, audio data or
whatever).
> regards
> --
> - Moritz Angermann / mind -
>
> -------------------------------------------------------------------
> This message is composed of 100% recycled electrons & photons only!
> -------------------------------------------------------------------
--
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
The Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
[EMAIL PROTECTED]
Mobile Phone: +61 (0)413 451 899 Home Phone: 02 9698 8615
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
enlightenment-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
