StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCustom Python Twisted protocol : good practices and complexity?
primarykey
Id
7134170
data
AcceptedAnswerId
7223578
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-20T19:32:57.523
FavoriteCount
0
LastActivityDate
2012-02-22T13:42:51.287
LastEditDate
LastEditorUserId
0
OwnerUserId
559939
ParentId
0
PostTypeId
1
Score
2
ViewCount
1976
LastEditorDisplayName
text
Body
I am currently working on a control system for Arduino type devices using Twisted,and have a bit of a design issue Here is how things are currently: (sorry in advance, might be a bit long) <ol> <li>to handle different type of devices (each having a different firmware & communication protocol ) i have a designed a "driver" system : <ul> <li>each driver is made of : <ul> <li>a "hardware handler class" : a wrapper around Twsited's serial class with a few added helper methods</li> <li>a custom serial protocol</li> </ul></li> </ul></li> </ol> 2- While implementing drivers for Reprap 3d printers (also based on arduino, also using a serial connection) with rather specific protocols (ie enqueue point, set temperature etc), i have started to wonder if i am placing the methods for handling those features (each having specific commands) in the right place.. This all leads me to my questions: I am not quite sure about the good practices as far as twisted protocols go , but having looked through the documentation / code of quite a few of them, it seems they tend to have relatively few methods <ul> <li>is this always the case? should the protocol only be used for very low level functions and in/out formatting and communication ? </li> <li>certain devices i want to manage have very clearly defined protocols (Makerbot etc), should i consider general protocol specifications to be a different thing then the actual Twisted protocol classes i am creating ? </li> </ul> Any advice, tips and pointers are more than welcome ! Thanks in advance.
Tags
<python><protocols><twisted><complexity-theory>
Title
Custom Python Twisted protocol : good practices and complexity?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMark Moissette
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCustom Python Twisted protocol : good practices and complexity?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POCustom Python Twisted protocol : good practices and complexity?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.