[DGD] More on asynchronous thread starts

[Felix A. Croes]

Shentino <shentino at gmail.com> wrote:

> Major differences in internal architectures then.
>
> I'm just having a hard time understanding the difference between DGD
> (or DGD MP)'s own code calling into LPC in response to an external
> event (i.e., new I/O or a new connection, or a callout going off), and
> an external package doing the same.

Well, for DGD it would be simple.  For DGD/MP it would involve defining
a new event type, and adding code to a number of switch statements
dealing with executing, committing, rescheduling or cancelling this
event.

The significant difference is not between DGD and add-on package, but
between DGD and DGD/MP.  If I were to mask those differences between
them for a networking package operating through the extension
interface, I would have to all but implement the networking package
myself, with something like DGD_ENABLE_OUTBOUND() in the interface;
precisely what I want to avoid.

Regards,
Dworkin