新书推介:《语义网技术体系》
作者:瞿裕忠,胡伟,程龚
   >>中国XML论坛<<     W3CHINA.ORG讨论区     计算机科学论坛     SOAChina论坛     Blog     开放翻译计划     新浪微博  
 
  • 首页
  • 登录
  • 注册
  • 软件下载
  • 资料下载
  • 核心成员
  • 帮助
  •   Add to Google

    >> XML网站展示,XML源代码,XML编程示例。 本版仅接受原创、转贴、网站展示,具体的技术交流请前往各相关版块。
    [返回] 中文XML论坛 - 专业的XML技术讨论区XML.ORG.CN讨论区 - XML技术『 XML源码及示例(仅原创和转载) 』 → 帮帮忙先,我这部分内容咋就看不懂呢? 查看新帖用户列表

      发表一个新主题  发表一个新投票  回复主题  (订阅本版) 您是本帖的第 7634 个阅读者浏览上一篇主题  刷新本主题   树形显示贴子 浏览下一篇主题
     * 贴子主题: 帮帮忙先,我这部分内容咋就看不懂呢? 举报  打印  推荐  IE收藏夹 
       本主题类别:     
     a00 帅哥哟,离线,有人找我吗?
      
      
      等级:大一新生
      文章:1
      积分:55
      门派:XML.ORG.CN
      注册:2004/4/3

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给a00发送一个短消息 把a00加入好友 查看a00的个人资料 搜索a00在『 XML源码及示例(仅原创和转载) 』的所有贴子 引用回复这个贴子 回复这个贴子 查看a00的博客楼主
    发贴心情 帮帮忙先,我这部分内容咋就看不懂呢?

    前面部分讲述了soap over https request的一些内容,然后就是这些了,我就是郁闷,看不懂呢?

       收藏   分享  
    顶(0)
      




    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/4/3 15:19:00
     
     a00 帅哥哟,离线,有人找我吗?
      
      
      等级:大一新生
      文章:1
      积分:55
      门派:XML.ORG.CN
      注册:2004/4/3

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给a00发送一个短消息 把a00加入好友 查看a00的个人资料 搜索a00在『 XML源码及示例(仅原创和转载) 』的所有贴子 引用回复这个贴子 回复这个贴子 查看a00的博客2
    发贴心情 
    附件没贴上,copy

    A LCS-Client requests a Location Query Service by issuing an HTTPS POST request towards the LES.
    The request line syntax is shown below.
    Request-line: POST SP host SP HTTP/1.1 CRLF
    The request must include the entity-header Content-length field as part of the request. The message body
    of the request will consist of three HTTP post parameters:
    • Context – This will contain the authentication details of the client (see chapter 2.4)
    • Method – This will identify the method that is to be invoked (consists of the name of the message
    being requested)
    • Body – This will contain the XML payload for the specified method (see chapter 3)
    The use of these parameters will allow an easier migration to SOAP, only minimal changes are required.
    This is because these parameters mirror the SOAP header and body sections but do not re-invent SOAP.
    Header and body have to correspond with XML and have to be urlencoded. The content-type of the
    request has to be "application/x-www-form-urlencoded":
    &Context=URLEncoded(HdrElement)&Method=Method&Body=URLEncoded(BodyElement)
    "Application/x-www-form-urlencoded" is the default content type. Forms submitted with this content type
    must be encoded as follows:
    • Control names and values are escaped. Space characters are replaced by `+', and then reserved
    characters are escaped as described in "Uniform Resource Locators" (T. Berners-Lee, L. Masinter,
    and M. McCahill, December 1994, [RFC1738]), section 2.2: Non-alphanumeric characters are
    replaced by `%HH', a percent sign and two hexadecimal digits representing the ASCII code of the
    character. Line breaks are represented as "CR LF" pairs (i.e., `%0D%0A').
    • The control names/values are listed in the order they appear in the document. The name is separated
    from the value by `=' and name/value pairs are separated from each other by `&'.
    More information about "application/x-www-form-urlencoding" can be found at http://w3.org/TR/REChtml40-
    971218, chapter 17.13.4.
    The answer will be included in the message body (see chapters 2.2.5 and 2.2.6) and the Content-length
    entity will be set to the length of the answer. The responses have no header part.
    Example HdrElement :

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2004/4/3 15:21:00
     
     GoogleAdSense
      
      
      等级:大一新生
      文章:1
      积分:50
      门派:无门无派
      院校:未填写
      注册:2007-01-01
    给Google AdSense发送一个短消息 把Google AdSense加入好友 查看Google AdSense的个人资料 搜索Google AdSense在『 XML源码及示例(仅原创和转载) 』的所有贴子 访问Google AdSense的主页 引用回复这个贴子 回复这个贴子 查看Google AdSense的博客广告
    2024/5/13 22:06:29

    本主题贴数2,分页: [1]

    管理选项修改tag | 锁定 | 解锁 | 提升 | 删除 | 移动 | 固顶 | 总固顶 | 奖励 | 惩罚 | 发布公告
    W3C Contributing Supporter! W 3 C h i n a ( since 2003 ) 旗 下 站 点
    苏ICP备05006046号《全国人大常委会关于维护互联网安全的决定》《计算机信息网络国际联网安全保护管理办法》
    62.500ms