Zope中使用XML-RPC

本文介绍如何利用XML-RPC与Zope进行交互,包括作为服务器和客户端的使用方式。详细解释了如何通过XML-RPC请求访问Zope对象及处理身份验证。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

How to use XML-RPC with Zope


How to use XML-RPC with Zope

It is well known that Zope speaks XML-RPC, however it has not until now been well known how to use XML-RPC with Zope.

Why use XML-RPC?

Because it's cool and allows sending structured data over HTTP, and most importantly because it is supported by other things besides Zope.

If you just want to exchange data between Zope processes, you might want to look into Zope's own RPC mechanism ZPublisher.Client.

Using Zope as an XML-RPC server

Every Zope object can respond to HTTP requests. This is Zope's object publishing philosophy. For example, a Folder will tell you the names of the items it contains when you call its objectIds method. So if the Folder is located at:

    http://www.example.com/Foo/Bar/MyFolder

you can request its contents by calling:

    http://www.example.com/Foo/Bar/MyFolder/objectIds

XML-RPC support works the same way. You can send an XML-RPC request to call the objectIds method directly to the MyFolder object:

        POST /Foo/Bar/MyFolder HTTP/1.0
        Content-Type: text/xml
        Content-length: 95

        <?xml version="1.0"?>
        <methodCall>
         <methodName>objectIds</methodName>
         <params/>
        </methodCall>

The results will be a list of contained object names.

All Zope objects are publishable and thus all are XML-RPC aware. There is no need to do anything special. In fact, Zope will encode your response so it is sufficient to return standard Python objects and Zope will marshal them into XML-RPC format.

XML-RPC and access control

Since XML-RPC runs over HTTP Zope still obeys authentication rules. This is one of Zope's great strengths--a simple and powerful security model. Zope carries this security model to XML-RPC. Your XML-RPC user agent should use basic authentication when accessing protected resources.

Fredrik Lundh's XML-RPC Python module doesn't come with support for sending requests with basic authentication, but it can easily be extended to do so.

Here's an example of how to do this that works for me:

    import string, xmlrpclib, httplib
    from base64 import encodestring

    class BasicAuthTransport(xmlrpclib.Transport):
        def __init__(self, username=None, password=None):
            self.username=username
            self.password=password

        def request(self, host, handler, request_body):
            # issue XML-RPC request

            h = httplib.HTTP(host)
            h.putrequest("POST", handler)

            # required by HTTP/1.1
            h.putheader("Host", host)

            # required by XML-RPC
            h.putheader("User-Agent", self.user_agent)
            h.putheader("Content-Type", "text/xml")
            h.putheader("Content-Length", str(len(request_body)))

            # basic auth
            if self.username is not None and self.password is not None:
                h.putheader("AUTHORIZATION", "Basic %s" % string.replace(
                        encodestring("%s:%s" % (self.username, self.password)),
                        "\012", ""))
            h.endheaders()

            if request_body:
                h.send(request_body)

            errcode, errmsg, headers = h.getreply()

            if errcode != 200:
                raise xmlrpclib.ProtocolError(
                    host + handler,
                    errcode, errmsg,
                    headers
                    )

            return self.parse_response(h.getfile()) 

Using XML-RPC as a client

Zope doesn't provide support in DTML to use XML-RPC as a client, but that doesn't mean that it can't be done.

Fredrik Lundh's XML-RPC Python module comes with Zope and you can use this in your External Methods or Zope Products to use XML-RPC as a client.

Here's an example:

    import xmlrpclib

    def getStateName(self, number):
        "Returns a state name given an integer state number"
        server_url="http://betty.userland.com"
        server=xmlrpclib.Server(server_url)
        return server.examples.getStateName(number)

To call this External Method you might want to create a form like this:

    <form action="getStateName">
    state number <input name="number:int">
    <input type="submit" value="get name">
    </form>

This example does not show it, but as always when writing code to access remote resources you need to take into account the possibility that the connection fail in one way or another, and it could take a very long time to get a response.

It would be an interesting project (hint, hint) to write an XML-RPC Method Zope Product that was smart about caching, etcetera. This would make XML-RPC available from DTML in a safe form.

 
内容概要:本文探讨了在MATLAB/SimuLink环境中进行三相STATCOM(静态同步补偿器)无功补偿的技术方法及其仿真过程。首先介绍了STATCOM作为无功功率补偿装置的工作原理,即通过调节交流电压的幅值和相位来实现对无功功率的有效管理。接着详细描述了在MATLAB/SimuLink平台下构建三相STATCOM仿真模型的具体步骤,包括创建新模型、添加电源和负载、搭建主电路、加入控制模块以及完成整个电路的连接。然后阐述了如何通过对STATCOM输出电压和电流的精确调控达到无功补偿的目的,并展示了具体的仿真结果分析方法,如读取仿真数据、提取关键参数、绘制无功功率变化曲线等。最后指出,这种技术可以显著提升电力系统的稳定性与电能质量,展望了STATCOM在未来的发展潜力。 适合人群:电气工程专业学生、从事电力系统相关工作的技术人员、希望深入了解无功补偿技术的研究人员。 使用场景及目标:适用于想要掌握MATLAB/SimuLink软件操作技能的人群,特别是那些专注于电力电子领域的从业者;旨在帮助他们学会建立复杂的电力系统仿真模型,以便更好地理解STATCOM的工作机制,进而优化实际项目中的无功补偿方案。 其他说明:文中提供的实例代码可以帮助读者直观地了解如何从零开始构建一个完整的三相STATCOM仿真环境,并通过图形化的方式展示无功补偿的效果,便于进一步的学习与研究。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值