[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP Serial Class (Second Attempt)
- Subject: Re: xAP Serial Class (Second Attempt)
- From: Stuart Booth
- Date: Fri, 21 Nov 2003 18:11:00 +0000
On Thu, 20 Nov 2003 21:19:29 -0000, "Paul Barrett"
<<a
href="/group/xAP_developer/post?postID=qBB9qovH4EoPX1kv_gCzy-OBu8fpWSxkcg998eaiDsTNjh8oVbc_i8e1KWoCSnllAaH5QVa2UN_NzBc1wAMDOA">pbarrett@r...</a>>
wrote:
>Do you think it would be better to use a single Setup function or have
>properties that have to be individually set before opening the port?
How about both? Setup stores all the parameters, they can all be
tweaked via the various Properties, and, say, Open uses these
parameters to configure/open the port. Close disconnects.
>Could you (or Kevin?) describe how the Serial Comms schema is to be
used.
>i.e. what should happen when a Serial.Setup block is received.
Off the top of my head I think it could either cause the port to be
opened as described, or those parameters are stored for later use.
If the former, then whenever data arrives is received from the port it
is sent on as a xAP message, subject to some sort of timeout
indicating the end of the data maybe. And when a xAP message to be
sent to the port arrives, it gets sent when appropriate.
In the latter case (when the setup block is stored for later use) I
was thinking more of a connect/send data/disconnect type setup, but I
don't know how useful that would be, as you couldn't necessarily
receive asynchronously unless there was a response anticipated.
S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=Yb5v7EmVAk5aO3dbdQ_3yVevuc_Ts6bstLOzTnmH6emRBG8ZLUqQB8UTQ_CStnHbK7ChO9pCVbVTug4-hkKYU0T9">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net
<a href="http://www.xapautomation.org/">http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/">http://www.xapframework.net/</a>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|