hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
I have an xml file in my application,
I have created an element using
Example goes like this.........
and i appeneded it by using append() method.
But how i can reflect this change to my xml file?
and one more thing is i want to create element with some other parameters....
<abc m=" " n=" ">
and i have m and n values as strings with me.
can anybody help me to create this element and write it to the existing xml file
as a child of an existing element?
Thanks in advance..
Forgot the famous last words? Access your message archive online at http://in.messenger.yahoo.com/webmessengerpromo.php
On 18 May 2004, the following message was posted to this mailinglist:
Jp Calderone exarkun at divmod.com wrote:
>Daniel Newton wrote:
> I have a simple XML-PRC server similar to the example below:
> from twisted.web import xmlrpc, server
> class Example(xmlrpc.XMLRPC):
> """An example object to be published."""
> def xmlrpc_add(self, a, b):
> """Return sum of arguments."""
> return a + b
> if __name__ == '__main__':
> from twisted.internet import reactor
> r = Example()
> reactor.listenTCP(7080, server.Site(r))
> I want to be able to get the address of the client that calls the
> method can anyone help me with this?
This solution didn't work because 'transport' isn't a property of the
I'm currently in the process of changing from a customized
SimpleXMLRPCServer to a twisted XMLRPC server solution and I need to
insert the client IP into the attributes passed to the called xmlrpc
method. Anyone who knows the answer and is willing to share the info?
I have a sample XMPP client with the following structure:
from twisted.words.protocols.jabber import client, jid
from twisted.internet import reactor
factory = client.basicClientFactory(myJid, myPasswd)
It works well, I can connect to the XMPP server. But I would appreciate
if some one could give me some hints on what's required to get the
client to connect using a secure SSL link.
I didn't want to hijack the 'Twisted Presentation Materials..' thread,
so I started this one ...
First off, in the other thread,
Glenn, you mentioned Storm. I have heard of Storm, but never got
any deeper that noticing that it is still a work in progress (maybe
things have settled down ?)
If anyone has anything to say on how it might be a good choice with
Twisted, please feel free to enlighten us!
But, I hoping to solve some immediate problems with Twisted and
SQLAlchemy, so ...
>> * A main "App Server", that controls high level access with "twisted.cred"
>> * Web frontend: "twisted.web2"
>> * Data: some "twisted.enterprise.adbapi", moving to SQLAlchemy.
> Interesting; how are you handling asynchrony in SA?
This is the issue that we're stilling unclear on, and I really
would like to know of the best way of integrating Twisted with SQLAlchemy.
Twisted devs / experts: Please, could you comment on the right way of
using Twisted and SQLAlchemy together.
Anyone: If anyone know of existing code that integrates Twisted and
SQLAlchemy nicely, please share!
RIght away I just went about the problem be wrapping each call
to SQLAlchemy in a "deferToThread" inside my "DatabaseManager" class.
At startup of my app, I make an instance of this class, and pass it to
each "avatar" (in "requestAvatar", in my portal)
Here is my Database Manager: (you will actually see that I 'turned
off' the deferToThread wrapping for now):
but I really haven't convinced myself that this is the best way of doing things.
Hell, it could be totally wrong, so if anyone has any advice, I would
be very appreciative!
> I'm aware of sAsync,
> but haven't looked much into it. (I'm a step or two behind you, actively
> using adbapi, and thinking about moving to SA when I get some breathing
I've looked into SAsync as well, but it is not totally clear to me
what the extra benefit of it is (again, anyone who has a good
description, please tell)
The main developer of sAsync use to post to this mailing list, but I haven't
seen him post in a fairly long while.
So, if others are thinking about using SQLAlchemy with Twisted, let's
discuss it more.
Thanks very much,
I would like to build a syslog(udp port 514) listener in twisted. The goal
is to make it compatible with syslog and syslog-ng, which may be configured
on a "client" to send log entries (as they occur) via udp (fire and forget)
to a remote server (my twisted server).
Is there already something out there that would do this or that would be a
I have written a python program that executes shell scripts on remote
computers using the twisted conch SSHChannel. Several shell scripts
are executed at once on several machines and the scripts range in
execution time from minutes to hours.
My question is regarding the behavior of Conch when it is shut down.
What i would like to do is to send a SIGINT or SIGKILL to the remote
script so that it can terminate in an orderly fashion. I am using the
channel.SSHChannel as a base class for my task. Is there a mechanism
in Conch for sending this signal?
Hi al i am new to twisted. I had been assigned a project on SSH.
the project is as follows.
i have to login to a remote Linux machine through Windows
i have to execute a shell script and print the output back in Windows
this needs to be done through SSH.
Any clues . please help. i need it urgently
Here's a summary of what Chris Armstrong, Itamar Shtull-Trauring,
and myself accomplished this past Sunday at the Twisted sprint.
Itamar took turns pairing with Chris and I. He and Chris worked on
creating command line tools to invoke the release automation libraries
which we've already written. You can find the results in a branch linked
from ticket #3439.
Itamar and I (and later Chris and I) worked on providing improved support
in Trial for inspecting warnings which have been emitted over the course
of a test. This is in support of the high-level deprecation API described
in ticket #3266.