[Tinyos-devel] Re: Python SDK

[Vlado Handziski]

If we aim for 2.1, we should first fix MIG because the code that is
currently generated is sometimes "unpythonic". Better support for message
encapsulation/decapsulation is also very important. I am not sure how far
these issues are addressed in the code from Matt, but they were the main
reason why we did not submit to the core our serial forwarder implementation
based on twisted python. We use internal workarounds for the above problems,
and pushing them into the core would have required rewriting major parts of
the TOSSIM python support. Another "nice to have" item would be to update
the rpc and the nesc modules from Kamin to handle the platform independent
message structures. This will give us a well rounded, powerful SDK.

Vlado

On 7/3/07, Philip Levis <pal at cs.stanford.edu> wrote:
>
> On Jul 3, 2007, at 1:35 PM, Matt Welsh wrote:
>
> > Thanks.
> >
> > In terms of (2), can you explain how the current python SDK is used?
> > Or give a use case that we can test things with?
> > Or would you be willing to quickly test that our stuff works with
> > something you have already set up?
>
> The test is injecting a packets into a TOSSIM simulation. The
> tutorial has an example of doing this.
>
> We're about to gear up to release 2.0.2; it might be a good idea to
> include your Python codes in the following release, 2.1. That will
> give it a few months in CVS for people to test and use it before
> release.
>
> Phil
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20070703/6273e044/attachment.html