<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Php on iniy.org</title><link>https://iniy.org/tags/php/</link><description>Recent content in Php on iniy.org</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 12 Apr 2024 11:00:19 +0000</lastBuildDate><atom:link href="https://iniy.org/tags/php/index.xml" rel="self" type="application/rss+xml"/><item><title>Find slow-queries in MySQL</title><link>https://iniy.org/2009/10/find-slow-queries-in-mysql/</link><pubDate>Wed, 14 Oct 2009 21:26:31 +0000</pubDate><guid>https://iniy.org/2009/10/find-slow-queries-in-mysql/</guid><description>&lt;p&gt;Often when a web-application seems slow it&amp;rsquo;s not (or not only) the parse time, but also or mayorly database speed. Most scripting-languages don&amp;rsquo;t act &amp;ldquo;intelligent&amp;rdquo; in parsing as it would be best for user experience, but go through the code line by line (whom would expect it otherwise?). So if you have a website containing some slow MySQL-Queries it seems as if all the page just takes a eternity to load. One step would be to put all the page loading into some seperate code-piece and load it later with ajax-technology. This gives a great boost in user-experienced speed, because the most parts of the website load and are already usable before the database content pops in. But otherwise often not the database is the problem, but bad written querys. But how to find them? Luckily mysql already provides us with a feature called slow-query-log which can be activated easily through my.cnf. So just look for this:&lt;/p&gt;</description></item><item><title>Useful PHP Ressources</title><link>https://iniy.org/2009/04/useful-php-ressources/</link><pubDate>Wed, 08 Apr 2009 19:10:48 +0000</pubDate><guid>https://iniy.org/2009/04/useful-php-ressources/</guid><description>&lt;p&gt;With the time this page should grow to a collection of useful ressources for PHP.&lt;/p&gt;&#10;&lt;h2 id="why-should-i-use-php"&gt;Why should I use PHP?&lt;a class="anchor" href="#why-should-i-use-php" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;it&amp;rsquo;s easy to learn and to use, imho easier than some other languages, like Java (don&amp;rsquo;t argue with me, almost everyone has his own opinion about this topic)&lt;/li&gt;&#10;&lt;li&gt;you have a fast experience of success, which motivates you to learn more&lt;/li&gt;&#10;&lt;li&gt;it&amp;rsquo;s easy to get the necessary preconditions&lt;/li&gt;&#10;&lt;li&gt;you can fastly develop webpages and web-applications&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="where-to-get-it"&gt;Where to get it?&lt;a class="anchor" href="#where-to-get-it" aria-label="Link to this section"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The easiest way to start is to get some cheap webspace, supporting PHP, like for example &lt;a href="http://net-housting.de" rel="noopener"&gt;http://net-housting.de&lt;/a&gt; for the german people around here. You just have to upload your scripts and access them over your browser.&lt;/p&gt;</description></item><item><title>OTRS Soap Interface</title><link>https://iniy.org/2009/03/otrs-soap-schnittstelle/</link><pubDate>Sun, 29 Mar 2009 20:39:24 +0000</pubDate><guid>https://iniy.org/2009/03/otrs-soap-schnittstelle/</guid><description>&lt;p&gt;Disclaimer: This are my first trys with the Soap Interface. If you&amp;rsquo;ve got better information just send it to me or post a comment, I will gladly update this documentation. I just wrote this article because there is almost no information about the OTRS Soap-Interface on the web. Perhaps it helps someone.&lt;/p&gt;</description></item></channel></rss>