blocks|key|1689255|text|我向我们的服务器发送PUT请求，正文中包含二进制数据，可能相当于10k文本记录，传输速度非常快。我可能想知道那里发生了什么，在一个与另一个的传输时间中，是否有什么东西可能误导了你。例如，post变量可能认为“传输”是请求的不同阶段。或者，如果您使用行/列名或其他名称向json结构添加了许多无关紧要的东西？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1689256|如果事实证明这是真的，并且每个方法都有相同的性能-我个人会选择在主体中使用结构化JSON，因为与一堆编码的post变量名相比，它似乎更清晰、更容易查看/调试。|1689257|此外，我不知道你的应用程序是做什么的，所以你的方法可能是完全合适的。但我可能会考虑是否可以按需发送数据，而不是一次性发送整个表。(当人们不回答我的问题并试图给我一些替代方法时，我会感到恼火，所以对这最后一点持保留态度！但似乎不寻常的是，一个人会接触到10k条记录-需要它们同时被发送到服务器)|1689258|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I send PUT requests to our server with binary data in the body, probably comparable to 10k text records and the transfer is very fast. I would probably wonder what was going on there, whether something might be misleading you in the transfer times of one vs another. For example the post vars might consider the "transfer" to be different phases of the request. Or perhaps if you added a lot of extraneous baggage to the json structure with row/column names or something?

If that turned out to be true and each method has equivalent performance - I personally would go with structured JSON in the body because it seems cleaner and easier to view/debug vs a bunch of coded post variable names.

Also - I have no idea what your app does so your approach may be totally appropriate. But I might look into figuring out if it was possible send data as-needed rather than sending an entire table all at once. (I get annoyed when people won't answer my question and try to give me some alternative method for doing things, so take this last bit with a grain of salt! But it does seem unusual that a human would have touched 10k records - requiring them to all be sent to the server at the same time)

blocks|key|1689270|text|你已经回答了你自己的问题。在开发软件时应该使用的代码的性能和质量之间存在一个合理的折衷。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1689271|因此，Json在两端(Javascript和PHP)都得到了支持，并为您的代码提供了更好的结构。|1689272|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|$]]

You have already answered your own question. 
There is a reasonable compromise between performance and Quality of code that should be used while developing Software.

So Json is supported on both side (Javascript and PHP), and provides a better struture in your code.

blocks|key|1689440|text|我认为有很多因素。您在哪种环境下工作，服务器和客户端是否在同一台PC上？你必须每天或每小时这样做吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1689441|其他项目是否在同一台服务器上，因此它们的响应速度会更慢？在一两个月内，您的var会超过10K吗？|1689442|如果像第一个选项那样发布数据，因为Javascript比PHP更快，所以有时您可能会丢失一些数据。|offset|length|style|CODE|1689443|如果您可以异步执行此操作，请查找RabitMQ，它是一个消息传递服务器，它在服务器准备就绪时执行任务(它做得也很快！)+http://www.rabbitmq.com/|1689444|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rabbitmq.com/^0|0|0|H|A|S|3|0|G|7|1O|O|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@$F|W|G|X|H|I]|$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$F|11|G|12|H|I]]|9|@$F|13|G|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I think there are many factors. On which environment are you working, the server and client are they on the same PC ? 
Do you have to do this every day or hour ? 

Are other projects on the same server so they can respond slower ? In one or two months do you will have more then 10K of vars ? 

If you post the data like in the first option, since <code>Javascript</code> is faster then <code>PHP</code> you can some times loose some data.

If you may do it asynchronously, look for <code>RabitMQ</code> it's a Messaging Server that do staff when the server is ready (it does it fast too!) 
<a href="http://www.rabbitmq.com/" rel="nofollow">http://www.rabbitmq.com/</a>

blocks|key|1902954|text|将其序列化为JSON字符串，但使用json_encode()和json_decode()，因为它要快得多。将变量放入一个对象中，然后序列化它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902955|另外，javascript应该做更多的工作，因为它将是客户端做的，这不会给服务器带来如此沉重的负载。|1902956|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|$]]

Serialise it to a JSON string but use json_encode() and json_decode() since it is a lot faster. Put the variables into an object and then serialise it.

Also, javascript should do more work since it would be the client doing it, which would not put the server under such heavy load.

blocks|key|1689840|text|我建议选择#1的一种变体。众所周知，JSON编码器和解码器存在but，并且存在跨平台问题，但发布数千个变量可能是一个问题。相反，您可以将所有post变量作为一个应用程序/x-www-form-urlencoded变量传递，然后使用parse_str()在PHP中对它们进行解码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1689841|Javascript：|1689842|data+=+"data="%2Bescape("v[0][0]="%2Bescape(v[0][0]));|code-block|syntax|javascript|1689843|PHP：|1689844|parse_str($_POST['data'],$data);|1689845|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I would suggest a variant of option #1. JSON encoders and decoders are known to be buggy and have cross-platform issues, but posting thousands of variables could be a problem. Instead you can pass all of your post variables as a single application/x-www-form-urlencoded post variable and then decode them in PHP with parse_str().

Javascript:

<pre><code>data = "data="+escape("v[0][0]="+escape(v[0][0]));
</code></pre>

PHP:

<pre><code>parse_str($_POST['data'],$data);
</code></pre>

I need to post table values of approx 200x50 (rows, cols) from jQuery to PHP. Two options:

1) Send it as array with 10,000 vars (increasing the php.ini max_input_vars).

2) Serialize the array to a JSON string, POST it as a string and decode back in PHP on the server side.

What is preferable? Any potential problems with the option 1?

Thanks

<hr>

PS. The update. After testing both potions on a large input tables up to 250x50 cells, it looks as the 1st option is much faster: 1-2 sec vs ~17-20sec for the JSON string. 

The bottleneck is the data transfer time to the server as object-to-JSON and back transactions are almost instant (a few milliseconds).

POST thousands of vars vs. a long JSON string: what is preferrable?

服务器

jQuery

JSON

我需要将大约200x50 (行，列)的表值从jQuery发布到PHP。有两个选项：1)将其作为包含10,000个var的数组发送(增加php.ini max_input_vars)。2)将数组序列化为JSON字符串，作为字符串发布，然后在服务器端解码回PHP。哪一种更可取？选项1有什么潜在的问题吗？谢谢PS。更新。在2...

问发布数千个var与一个长JSON字符串:哪个更可取？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问发布数千个var与一个长JSON字符串:哪个更可取？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问发布数千个var与一个长JSON字符串:哪个更可取？
EN