On 2/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> If no one objects I'll put this in CVS tonight.
It's in CVS now. Please test it. I'm going to be out until next week
so I won't be able to reply to mail.
Thanks,
Pedro.
On 2/13/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Hmm,
>
> We're not testing the owserver, just the clients. How about write returns an
> error if you don't write the set value?
We're not testing the server but we need to test if the writes
actually do something. Returning an error should be e
On 2/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
Have you thought about writable atributes? For full testing the --test
device must actually save the value and return it if it's read.
Pedro.
Hmm,
We're not testing the owserver, just the clients. How about write returns an
error if y
On 2/13/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Pedro, your note suggests the answer!
>
> While --fake is good for random responses, we want predictable responses to
> test against.
>
> How about --tester as a simulated adapter.
> 1. It would return known devices
> 2. It would return kno
On 2/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
Bigger stuff:
- Unit test this. I was going to write a mock owserver replacement
to use for testing but then I saw that owserver supports a fake
backend that gives random values. The problem with this is that if I
do someSensor.templow =
On 2/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
If no one objects I'll put this in CVS tonight.
I forgot to attach the code. Here it is.
Pedro.
connection.rb
Description: application/ruby
-
Using Tomcat but need
On 2/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> Smaller stuff:
> - Abstract the messages into a class of their own so that instead of
> pack/unpack we can do "msg.flags = whatever". Should make the code
> prettier and probably simpler.
This is done now and should make implementing pers
On 2/9/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
I wanted to use owfs in a Ruby project so I decided to port the Python
ownet client to Ruby.
Attached is a more or less straight port of the Python version of
ownet. I don't know if someone wants to check this first before I put
it into CVS
On 2/11/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> New documentation on persistent connections:
> http://www.owfs.org/index.php?page=persistent-connections
(...)
> Yes, owserver supports persistent connections, but they must be REQUESTED
> and GRANTED. (It's only a single bit to signal this).
New documentation on persistent connections:
http://www.owfs.org/index.php?page=persistent-connections
On 2/11/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
On 2/10/07, Peter Kropf <[EMAIL PROTECTED]> wrote:
> Hi Pedro -
>
> I'm (slowly) in the process of implementing the changes needed for
>
On 2/10/07, Peter Kropf <[EMAIL PROTECTED]> wrote:
> Hi Pedro -
>
> I'm (slowly) in the process of implementing the changes needed for
> persistent tcp support in the ownet Python module. It'll take me a few
> more days but I'll see about incorporating your suggestions into the
> code also.
Great.
On 2/10/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Persistent tcp connections are a new optional feature. There has been a
> recent string that explains them.
Ok, I'll look into it.
> And we'd love to have the ruby code included!
Cool. I'll clean it up and submit it.
Pedro.
Hi Pedro -
I'm (slowly) in the process of implementing the changes needed for
persistent tcp support in the ownet Python module. It'll take me a few
more days but I'll see about incorporating your suggestions into the
code also.
Thanks. Sorry for the delay but work's been really busy the last
cou
Hi Pedro,
Peter Kropf wrote the python support and will be interested in your work,
I'm sure. You've been working very intensely. It may take more than 2 days
fpr him to respond.
Persistent tcp connections are a new optional feature. There has been a
recent string that explains them.
And we'd l
On 2/9/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> I wanted to use owfs in a Ruby project so I decided to port the Python
> ownet client to Ruby.
I've just about finished this. I have a general question about ownet.
The python client creates a new TCP connection for each command that
it send
On 2/9/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> In __init__,py there's this piece of code (line 379):
>
> namelist = ','.join(list)
> #print 'Sensor.sensors namelist(%s)' % str(namelist)
> for branch_entry in namelist.split(','):
Right below it there's:
try:
self._connection.read(bran
On 2/9/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
> I wanted to use owfs in a Ruby project so I decided to port the Python
> ownet client to Ruby.
In __init__,py there's this piece of code (line 379):
namelist = ','.join(list)
#print 'Sensor.sensors namelist(%s)' % str(namelist)
for branch_e
17 matches
Mail list logo
