Hi Ajay,
On Sun, Aug 23, 2015 at 09:15:02AM +0530, Ajay Garg wrote:
>
> First of all, let me present the scenarios where we intend to run our code
> ::
>
> a)
> Our client-application, deployed on a vanilla Linux-Desktop, using WIFI to
> communicate with a "normal" server running on a public IP-
Hi Ajay,
On Sun, Aug 23, 2015 at 07:38:16AM +0530, Ajay Garg wrote:
>
> In the application that we have designed and coded so far, everything has
> been kept single-threaded only (so as now to have any dependency on any
> third-party embedded-device-vendors).
>
> So, it turns out, that we "do"
Hi All.
On more thought, it occurs to me that at a minimum, it should be feasible
to have the Layer3 (IP) Layer functionality at the application itself, if
we are just concerned with adding/stripping the IP to/from the packet
just-before-sending/just-after receiving it to/from Layer 2 (more so whe
