[Pybeep-devel] Notes on todo's

[Gabe W. <gw...@wa...>]

We've had a *very* productive discussion on #beepnik today about the next
priorities. In particular, we've uncovered areas that are going to diverge
from the java beepcore both for language issues (certain things are better
done differently in python) and for architectural reasons (I wanted to
have a scheduler handle the ordering of frames written to a peer instead
of a "first produced, first written" model - this would allow for
pluggable strategies for perhaps prioritizing output from certain channels
to a peer).

This is the list we came up with of priorities (this list only makes sense
if you read the chat logs!):

1) Make DataQueue an actual class so we can deal with it properly

2) Decided on an interface for DataQueueStream and whether we need a
InputDQS and OutputDQS

3) Implement the mime-parsing stuff (there is code in datastream
for general header-parsing a la HTTP -- is that needed?)

4) Work on the outgoing message queues and refactor sendToPeer in
channel.py

5) Work on incoming message queue and any events that need to
created/generated

6) Work on session and scheduler interfaces

4,5,6 can happen in parallel

We identified that most of the DataStream (not DataQueueStream) stuff is
cruft from the java port that we aren't going to use.

Huston Franklin (frmly of Invisible Worlds, coauthor of java beepcore) has
joined as a committing contributor.

If you are interested in our lengthy discussion today, please see
http://beepnik.wiredobjects.com/logs/2002-02-21.txt

As always, chat logs and urls (from the chump bot) can be found at
http://beepnik.wiredobjects.com

	-Gabe (your ill beepnik)

-- 
Gabe Wachob                   gw...@wa...
Personal                   http://www.wachob.com
CTO, WiredObjects    http://www.wiredobjects.com