blocks|key|1613251|text|您实际上并不需要HTTP客户端本身。HTTP是一种非常简单的基于文本的协议，如果需要，您可以自己实现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1613252|也就是说，您可能不需要自己实现它。如果他们有一个TCP栈和一个标准的套接字库，您可能会找到一个简单的C库(比如this+one)，它为您包装了HTTP或SOAP功能。然后，您可以将该库构建到您的应用程序中。|offset|length|1613253|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/projects/csoap/^0|0|1J|8|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

you don't really need an HTTP client per-se. HTTP is a very simple text-based protocol that you can implement yourself if you need to.

That said, you probably won't need to implement it yourself. If they have a TCP stack and a standard sockets library, you can probably find a simple C library (such as <a href="http://sourceforge.net/projects/csoap/" rel="nofollow noreferrer">this one</a>) that wraps up HTTP or SOAP functionality for you. You could then just build that library into your application.

blocks|key|1496711|text|您可以在套接字上实现一个简单的http客户端(这里是如何在ruby：http://www.tutorialspoint.com/ruby/ruby_socket_programming.htm中实现的示例)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1496712|这可能取决于您的嵌入式设备上可用的技术-如果您可以轻松地使用JSON或XML，那么使用上面的webservice方法可能对您有效。|1496713|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tutorialspoint.com/ruby/ruby_socket_programming.htm^0|Y|1Q|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You can implement a trivial http client over sockets (here is an example of how to do it in ruby: <a href="http://www.tutorialspoint.com/ruby/ruby_socket_programming.htm" rel="nofollow noreferrer">http://www.tutorialspoint.com/ruby/ruby_socket_programming.htm</a> )

It probably depends what technology you have available on your embedded devices - if you can easily consume JSON or XML then a webservice approach using the above may work for you.

blocks|key|91673|text|基本HTTP协议并不是一个很难手工实现的协议。它是一个基于文本和行的协议，除了有效负载之外，服务器与“原始的、火腿握紧的”客户端工作得很好，这是一个简单的客户端所需要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91674|如果你可以只使用一个子集，那么只需简单地编写它就可以了。|91675|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Basic HTTP is not a particularly difficult protocol to implement by hand. It's a text and line based protocol, save for the payload, and the servers work quite well with "primitive, ham fisted" clients, which is all a simple client needs to be.

If you can use just a subset, likely, then simply write it and be done.

blocks|key|311843|text|如果您的服务器提供的是简单文件，那么嵌入式设备实际上只需要发送一个HTTP+GET+request+(可能带有一些额外的数据来标识设备，这样服务器就可以知道要发送哪个固件版本)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|311844|从这里开始，读取来自嵌入式设备套接字的原始数据就非常简单了--您可能只需要忽略响应中的HTTP头，也可以将服务器配置为不为这些请求发送它。|311845|entityMap|0|LINK|mutability|MUTABLE|url|http://djce.org.uk/dumprequest^0|X|G|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

If your servers are serving simple files, the embedded devices really only need to send an <a href="http://djce.org.uk/dumprequest" rel="nofollow noreferrer">HTTP GET request</a> (possibly with a little extra data identifying the device, so the server can know which firmware version to send). 

From there, it's pretty much a simple matter of reading the raw data coming in on the embedded device's socket -- you might need to only disregard the HTTP header on the response, or you could possibly configure your server to not send it for those requests.

My company is planning on implementing a remote programming tool to configure embedded devices in the field. I assumed that these devices would have an HTTP client on them, and planned to implement some REST services for them to access. Unfortunately, I found out that they have a TCP stack but no HTTP client. One of my co-workers suggested that we try to send “soap packets” over port 80 without an HTTP client. The devices also don’t have any SOAP client. Is this possible? Would there be implications if there was a web server running on the network the devices are connected to? I’d appreciate any advice or best practices on how to implement something like this.

Advice on web services without HTTP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的公司正计划实现一个远程编程工具，用于现场配置嵌入式设备。我假设这些设备上有一个HTTP客户端，并计划实现一些REST服务以供它们访问。不幸的是，我发现他们有一个TCP堆栈，但没有HTTP客户端。我的一位同事建议我们尝试在没有HTTP客户端的情况下通过端口80发送“soap数据包”。这些设备也没有任何SOAP客户端。...

问关于不使用HTTP的web服务的建议
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问关于不使用HTTP的web服务的建议EN