[e-lang] Causeway JSON format doc? (attn Tyler Close and Terry Stanley)
tyler.close at gmail.com
Fri Aug 1 19:01:38 CDT 2008
On Fri, Aug 1, 2008 at 4:46 PM, Tyler Close <tyler.close at gmail.com> wrote:
> On Fri, Aug 1, 2008 at 4:17 PM, Kevin Reid <kpreid at mac.com> wrote:
>> On Aug 1, 2008, at 18:17, Tyler Close wrote:
>>> On Fri, Aug 1, 2008 at 9:11 AM, Kevin Reid <kpreid at mac.com> wrote:
>>>> So Causeway now labels events in its tree by the first entry in their
>>> I think the last version I used did so.
>> I'm not sure this is a good idea.
>> It seems to me that, unless I explicitly twiddle the trace to support
>> this usage, the top-of-stack on a Send is going to be message-queuing
>> internals, and the top-of-stack on a Got is going to be generic
>> message handling code (since the target hasn't been invoked yet),
>> neither of which is going to be especially informative in an event list.
> In the Waterken Server implementation, I twiddle the trace to remove
> all the infrastructure code, leaving only the application code. I
> think this makes the trace much more usable for application
> developers. For example, see the sample traces at:
> You'll notice there's no extra cruft in there beyond the application code.
On a Got, the trace consists of a single call site that is dummied up
to be the first line of the invoked application method. In addition to
providing a good name to Causeway, this also lets the programmer see
what concrete implementation was invoked by the virtual method call.
More information about the e-lang