blocks|key|2475986|text|这完全取决于您的应用程序是如何构建的，在堆栈溢出时发生的情况是，JavaScript捕获了删除链接单击，并发出了一个Ajax请求来删除该帖子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2475987|您可以使用JavaScript库轻松捕获与选择器规则匹配的所有元素的单击。|2475988|然后，您可以使用Ajax向PHP脚本发送请求，以完成SQL工作。|2475989|另外，理想情况下，您不会使用GET删除条目，而是使用POST，但这是另一个故事。|2475990|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It all depends on how your application is built, what happens at Stack Overflow is that the delete link click is caught by JavaScript and an Ajax request is being made to delete the post.

You can use a JavaScript library to easily catch clicks on all elements that match your selector rule(s).

Then you can use Ajax to send a request to the PHP script to do the SQL work.

On a side note, ideally you would not use GET for deleting entries, but rather POST, but that's another story.

blocks|key|950029|text|如果没有href="..."属性，则没有JavaScript链接就无法工作，这是非常正确的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|950030|通常，JavaScript所做的是使用阿贾克斯与服务器联系:这是异步JavaScript和XML。它与服务器联系，就像您直接访问页面一样，但在后台进行，而不更改浏览器显示的页面。|950031|然后，服务器端页面可以执行所需的任何处理。无论是哪种情况，都是由PHP来完成的，而不是JavaScript。|950032|讨论效率时的主要区别在于，在传统模型中，在将表单POST到page中，在完成请求后，必须将整个页面呈现为“结果”，使用<head>完成，并包含所有可见的页面内容。|950033|但是，当您使用AJAX执行后台请求时，访问者从未看到结果。事实上，它通常甚至不是一个人类可读的结果。在此模型中，只需传输JavaScript可用于更改页面的新信息。|950034|这就是为什么人们通常认为AJAX比传统模型“更高效”：更少的数据需要来回传输，而浏览器(通常)需要做更少的工作才能将数据显示为页面的一部分。在您的“删除”示例中，唯一的通信是"delete=777“，然后可能是"success=true”(仅稍微简化一下)- a的微小数量的信息来进行通信，效果如此之大！|950035|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/AJAX^0|4|A|0|J|4|0|0|0|O|4|1N|6|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1B|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

You're quite correct that absent an <code>href="..."</code> attribute, the link would not work without JavaScript.

Generally, what that JavaScript does is use <a href="http://en.wikipedia.org/wiki/AJAX" rel="nofollow noreferrer">AJAX</a> to contact the server: that's Asynchronous JavaScript and XML. It contacts a server, just as you would by visiting a page directly, but does so in the background, without changing what page the browser is showing. 

That server-side page can then do whatever processing you require. In either case, it's PHP doing the work, not JavaScript.

The primary difference when talking about efficiency is that in a traditional model, where you <code>POST</code> a form to a PHP page, after finishing the request you must render an entire page as the "result," complete with the <code>&lt;head&gt;</code>, and with all the visible page content.

However, when you're doing a background request with AJAX, the visitor never sees the result. In fact, it's usually not even a human-readable result. In this model, you only need to transfer the new information that JavaScript can use to change the page.

This is why AJAX is usually seen as being "more efficient" than the traditional model: less data needs to travel back and forth, and the browser (typically) needs to do less work in order to show the data as part of the page. In your "delete" example, the only communication is "delete=777" and then perhaps "success=true" (to simplify only slightly) — a tiny amount of information to communicate for such a big effect!

blocks|key|950068|text|绑定以"delete_post_“开头的锚上的单击事件，并使用该事件启动Ajax请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|950069|$("a[id%5E='delete_post_']").click(function(e){
++e.preventDefault();+//+to+prevent+the+browser+from+following+the+link+when+clicked
++var+id+=+parseInt($(this).attr("id").replace("delete_post_",+""));

++//+this+executes+delete.php?questionID=5342,+when+id+contains+5342
++$.post("delete.php",+{+questionID:+id+},
++++function(data){
++++++alert("Output+of+the+delete.php+page:+"+%2B+data);
++++});

});|code-block|syntax|javascript|950070|使用上面的$.post()进行//UPDATE，JavaScript代码在后台调用一个类似delete.php?id=3425的页面。如果delete.php包含任何输出，它将在数据变量中对您可用。|offset|length|style|CODE|950071|这是使用jQuery。在作品上阅读所有关于它的内容。|950072|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.jquery.com/How_jQuery_Works^0|0|0|5|8|19|I|1X|A|0|C|2|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$I|16|J|17|1|18]]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Bind a click event on the anchor which start with "delete_post_" and use that to start an Ajax request.

<pre><code>$("a[id^='delete_post_']").click(function(e){
 e.preventDefault(); // to prevent the browser from following the link when clicked
 var id = parseInt($(this).attr("id").replace("delete_post_", ""));

 // this executes delete.php?questionID=5342, when id contains 5342
 $.post("delete.php", { questionID: id },
 function(data){
 alert("Output of the delete.php page: " + data);
 });

});
</code></pre>

//UPDATE
With the above <code>$.post()</code>, JavaScript code calls a page like <code>delete.php?id=3425</code> in the background. If <code>delete.php</code> contains any output it will be available to you in the data variable.

This is using jQuery. Read all about it at <a href="http://docs.jquery.com/How_jQuery_Works" rel="nofollow noreferrer">http://docs.jquery.com/How_jQuery_Works</a>.

blocks|key|2476109|text|您的方法不安全，因为用户代理可能无意中在没有用户干预的情况下爬行链接和删除post。例如，Googlebot可能会这样做，或者用户的浏览器可能会预取页面以加快响应时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2476110|来自RFC+2616:超文本传输协议--+HTTP/1.1|offset|length|2476111|9.1.1安全方法
实现者应该意识到，软件在他们通过互联网进行的交互中代表了用户，并且应该小心地让用户知道他们可能采取的任何可能对他们自己或其他人有意想不到意义的行动。
特别是，公约规定，GET和HEAD方法除了检索之外，不应具有采取其他行动的意义。这些方法应该被认为是“安全的”。这允许用户代理以一种特殊的方式表示其他方法，如POST、PUT和DELETE，从而使用户意识到正在请求一个可能不安全的操作。
当然，不可能确保服务器执行GET请求不会产生副作用；事实上，一些动态资源认为这是一个特性。这里的重要区别是用户没有要求产生副作用，因此不能对其负责。|blockquote|2476112|正确的方法是使用按钮通过POST提交表单，或者使用JavaScript进行删除。JavaScript可以提交隐藏表单，导致重新加载整个页面，或者使用Ajax进行删除而不重新加载页面。无论哪种方式，重要的一点是避免在页面中有可能无意中由不知情的用户代理触发的裸露链接。|2476113|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html^0|0|2|R|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Your method is not safe as a user agent could inadvertently crawl the link and delete the post without user intervention. Googlebot might do that, for instance, or the user's browser might pre-fetch pages to speed up response time.

From <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html" rel="nofollow noreferrer">RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1</a>

<blockquote>
 <h3>9.1.1 Safe Methods</h3>
 
 Implementors should be aware that the
 software represents the user in their
 interactions over the Internet, and
 should be careful to allow the user to
 be aware of any actions they might
 take which may have an unexpected
 significance to themselves or others.
 
 In particular, the convention has been
 established that the GET and HEAD
 methods SHOULD NOT have the
 significance of taking an action other
 than retrieval. These methods ought to
 be considered "safe". This allows user
 agents to represent other methods,
 such as POST, PUT and DELETE, in a
 special way, so that the user is made
 aware of the fact that a possibly
 unsafe action is being requested.
 
 Naturally, it is not possible to
 ensure that the server does not
 generate side-effects as a result of
 performing a GET request; in fact,
 some dynamic resources consider that a
 feature. The important distinction
 here is that the user did not request
 the side-effects, so therefore cannot
 be held accountable for them.
</blockquote>

The right way to do this is to either submit a form via POST using a button, or use JavaScript to do the deletion. The JavaScript could submit a hidden form, causing the entire page to be reloaded, or it could use Ajax to do the deletion without reloading the page. Either way, the important point is to avoid having bare links in your page that might inadvertantly be triggered by an unaware user agent.

blocks|key|2476143|text|您要查找的url在js代码中。就我个人而言，我会有一个标识每个标签的一个特定的帖子，评论.或者随便什么，然后在每一个上都有一个class="delete_something“，然后使用javascript将其发布到正确的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2476144|就像这样：|2476145|<a+href="#"+class="delete_post"+id="post_111"+title="Delete+Post">Delete</a>

<script+type="text/javascript">
jQuery('a.delete_post').live('click',+function(){

++++jQuery.post('delete.php',+{id:+jQuery(this).attr('id')},+function(data){
++++++++//do+something+with+the+data+returned
++++})
});
</script>|code-block|syntax|javascript|2476146|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The url you are looking for is in the js code. Personally I would have an id that identifies each &lt;a&gt; tag with a specific post, comment... or whatever, and then have a class="delete_something" on each one, this then posts to the correct place using javascript.

Like so:

<pre><code>&lt;a href="#" class="delete_post" id="post_111" title="Delete Post"&gt;Delete&lt;/a&gt;

&lt;script type="text/javascript"&gt;
jQuery('a.delete_post').live('click', function(){

 jQuery.post('delete.php', {id: jQuery(this).attr('id')}, function(data){
 //do something with the data returned
 })
});
&lt;/script&gt;
</code></pre>

Which of the following code is better in building a <code>delete</code> -action for removing a question?

<h1>1 My code</h1>

<pre><code>&lt;a href='index.php?delete_post=777&gt;delete&lt;/a&gt;
</code></pre>

<h1>2 Stack Overflow's code</h1>

<pre><code>&lt;a id="delete_post_777&gt;"&gt;delete&lt;/a&gt;
</code></pre>

I do not understand completely how Stack Overflow's delete -button works, since it points to no URL. 
The <code>id</code> apparently can only be used by CSS and JavaScript.
Stack Overflow apparently uses JavaScript for the action.

<ol>
<li>How can you put start the <code>delete</code> -action based on the content of CSS -file by JavaScript?</li>
<li>How can you start a SQL delete -command by JavaScript? I know how you can do that by PHP, but not by JavaScript.</li>
</ol>

To build a `Delete` -button efficiently with JavaScript / PHP

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

下面哪一种代码在构建用于删除问题的delete -action中更好？1我的代码<a href='index.php?delete_post=777>delete</a>2堆栈溢出的代码<a id="delete_post_777>">delete</a>我不完全理解堆栈溢出的删除-button是如何工作的，因为它没...

问使用-button / JavaScript高效构建‘`Delete`’JavaScript
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用-button / JavaScript高效构建‘`Delete`’JavaScriptEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用-button / JavaScript高效构建‘`Delete`’JavaScript
EN