],
Outboxes = [outbox, signal])
Again, please take with liberal doses of salt.
Cheers,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send email to kamaelia
;-) :-)
No worries! I really need a holiday myself so I can fully appreciate
how necessary some away time can be.
Thanks,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send
than a little
flagrant idea stealing from CPAN/CTAN :-)
Sounds good to me. And thank you!
--Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send email to kamaelia
and
stores it in a list. This is by design not thread-safe as it is
intended only to be accessed after the Kamaelia pipeline has
terminated.
I look forward to any thoughts or comments you might have on these components.
-- Steve
--~--~-~--~~~---~--~~
You received
subversion tree but they also need to manually patch it
as well.
I can understand longer delays between feature based releases, but it
would be great if there was at least a way to streamline getting
corrective fixes into subversion.
Thanks,
Steve
On Mar 26, 8:09 am, Michael Sparks spark
exceptions
- micro-optimize tcp connection timeout to take delay math out of
loop
- micro-optimize tcp delay before connect to take math out of loop
Cheers,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia
/ outboxes whose activity
should not unpause the component.
--Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send email to kamaelia@googlegroups.com
To unsubscribe from
On Mar 4, 8:59 am, Steve unetright.thebas...@xoxy.net wrote:
It's dumb bug - thanks for catching it - I'll squash the problem in other
files.
I found both problems with the UDP and Selector code. As mentioned
previously, all the components in UDP_ng (and UDP too I think) need
the following
as it is today
2) In safeConnect, sock.settimeout(20)
3) sock.connect() as it is today
4) sock.settimeout(0) after the connection
It seems like this would allow you to have a timeout honored for the
connect operation without impacting non-blocking data operations post-
connect.
--Steve
some timeout, windows machines won't get
sane connection refused errors. And I can understand an aversion to
10 secoonds, but what about 1 second? A half a second? What is the
shortest we can block and still get (somehow) a useful error? I'm
going to keep experimenting.
--Steve
and use timeouts?
--Steve
On Mar 3, 12:30 pm, Steve unetright.thebas...@xoxy.net wrote:
Michael,
Thank you for your detailed explanation. I did see what you checked
in before I started looking at the timeout capabilities. I have to
think there is a better way still. I've been doing some
On Mar 3, 2:11 pm, Steve unetright.thebas...@xoxy.net wrote:
What should happen in my opinion is that at some point we should go
from getting WSAEINVALID back to a single EWOULDBLOCK when the first
connection is refused and then a brand new connection is started. But
we never do see
class TCPClient(Axon.Component.component):
def __init__(self,host,port,delay=0,connect_timeout=60):
self.connect_timeout = connect_timeout
...
connect_start = time.time()
while not self.safeConnect(sock,(self.host, self.port)):
Thinko, I meant:
waitTill = time.time() + self.connect_timeout
while not self.safeConnect(sock,(self.host,
self.port)):
if self.shutdown():
return
if time.time() = waitTill:
like despite sending the messages
prior to the close, the messages are read and acted upon after the
close. Which is probably why sometimes it barfs when it tries to do
something with the descriptor and it doesn't know the socket is
closed.
Thanks,
Steve
On Mar 2, 1:36 pm, Steve unetright.thebas
SingleShotHTTPClient('http://66.102.7.99:8000/') = OK
SingleShotHTTPClient('http://localhost:8000/') = OK
Cheers,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send
Oh heck, this bug is in the underlying TCPClient! After spending days
developing against localhost, I now find that I can't go live without
having to do manual name resolution. :(
--Steve
On Mar 2, 1:39 am, Steve unetright.thebas...@xoxy.net wrote:
FYI
SingleShotHTTPClient on windows
problem with UDP sockets because I was about to detail an
inability to shutdown unconnected UDP peers.
Thanks,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send email
reacting to the
bugs that I've been describing in other threads. If we could identify
why refused connections are infinite looping on vista and why
unconnected udp peers are refusing to shutdown, there might be no need
for this kind of time terminating component.
--Steve
this be related to the TCP ignored connection bug
that I was describing in another thread?
Thanks,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post to this group, send email to kamaelia
exposing a
uniform framework interface. My brain doesn't fit twisted, but now
I'm starting to appreciate what he was talking about.
Thanks,
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
kamaelia group.
To post
Small update to reduce periodic drift in PeriodicTick class. Also
removed an accidentally included producerFinished signal from the same
class.
http://pastebin.com/m351a87c9
--Steve
On Feb 27, 9:45 am, I wrote:
I've been having trouble with the SimpleServer getting in a bad state
method unless you are
going to be initializing some instance variables.
7) No line continuation \ is needed inside a multiline comment
.
With all those changes, you have: http://pastebin.com/m1fdf518e
Good Luck!
--Steve
On Mar 1, 8:31 pm, Gloria W strang...@comcast.net wrote:
Hi all,
I
expired. Now the embedded component
can return early and the timer will shutdown, allowing the pipeline or
scheduler to finish without waiting for the TTL timer to run its
course.
http://pastebin.com/m4b46410d
--Steve
On Feb 27, 1:01 pm, Steve unetright.thebas...@xoxy.net wrote:
That'll teach
if anyone would care to comment on the design of this
component. I'm very new to Kamaelia, so I'm still trying to get a
feel for the best style.
http://pastebin.com/f3ca145c7
Thank you!
Steve
--~--~-~--~~~---~--~~
You received this message because you are subscribed
That'll teach me to try to post a code sample while my flight is
boarding. I forgot the SingleTick timer class used. Here's an
updated posting:
http://pastebin.com/m43f84692
Thanks,
Steve
On Feb 27, 9:45 am, I wrote:
I've been having trouble with the SimpleServer getting in a bad state
26 matches
Mail list logo
