Daniel0

I agree with Juan, you should always learn the basics of a language before you try to use a framework for that language.

The starter of this topic has been banned (for the fifth time) so there is no point in continuing his topic. Locked.

Done.

That's strange. Does anyone else have that problem? It works for me.

That's just the HTTP protocol (and other protocols as well). There are protocols which have state such as IRC, FTP, SSH, BitTorrent and many others.

You don't need a tutorial that teaches you how to build a specific system. You need to combine different concepts into one project. You may find this blog post by thorpe useful.

Ah, well... that changes quite something. I run 127.0.0.1, does that count?

I run PHP Freaks' servers although neither the website nor the servers are owned by me. Additionally i run my own VPS which currently hosts no websites.

Some PHP error probably occurred. Make sure display_errors is set to true and set error_reporting to E_ALL and check again. When you're done, turn off display_errors again. You could also check your error log.

Sorry, we don't delete accounts.

I know I'm just being picky, but in natural science it is not possible to prove anything (except in mathematics, but it doesn't count in this case). There are basically two methods. There is the inductive method where you through observations and experiments (your empirical data) can infer a theory. For instance, you could take an object, hold it out and release it a lot of times. All of the times the object dropped down and therefore you can, by observation, conclude that there must be a force pulling it downwards. BUT, you cannot possibly prove that the next time you release it then it will drop as well (although it is highly likely). Therefore it's impossible to prove anything. You can have a theory and that may be the "working" theory until someone else finds a better theory. Additionally there is the hypothetical-deductive method which essentially works the other way around. Here you make a hypothesis and then you make observations and experiments to check if your hypothesis fits with what you've found out. You can then conclude whether your hypothesis was valid or invalid. Using the "drop the object" analogy again you can "guess" that some force is pulling objects down thus making them drop to the ground instead of idly hovering in the air. Then you drop some objects repeatedly and conclude that there must be. This is obviously a very simple example, but it's merely to show the point. Also, both of these methodologies are equally valid to use. Man... this ended up longer than I intended. Sorry for going somewhat off-topic, but I just thought you might find it useful as an aspiring amateur physicist Edit: http://xkcd.com/386/

Actually it gives you power in a way as well. Say you usually use framework X, then you'll be able to overtake other projects written using framework X fairly easily because they're both written in the same way. Internally in a company that could also be a way of enforcing the way applications are written by using a standardized format so all the developers and all future developers will be able to understand code written by other people without much effort.

I haven't used mootools, but it's one of the more popular Javascript frameworks so I guess it's okay. I would recommend you to learn basic Javascript before using a framework, but it's probably not necessary. For instance, most rails developers have probably never written a standalone ruby script. Still though, I think it would be a good idea to get the basics straight before starting with a framework.

I watched some video by a YouTube engineer once. He said that they use Python. I've also seen some pages on Google that end with .py.

In that case you should create your own operating system, web server and language to ensure that you can always fix any bugs. Also, I'm not saying that one should just start using the frameworks instead of learning the language, but once you've done that then you might benefit from using a framework (be it your own or one that is written by someone else). The benefit of using a third-party framework is that it has been tested and used by a lot of people and therefore there are a lot of eyes looking on it compared to your own framework which you likely are the sole developer of. That's also why some people argue that open source software is better than proprietary closed source software; more people are looking at it.

That doesn't make any sense at all... Well then make your own Javascript framework. The before-mentioned ones were merely examples of frameworks. They are by no means definitive nor required. Which cross-browser issues do you not feel that jQuery has addressed adequately?

That's why people use frameworks such as jQuery (my favorite), prototype, mootools, etc. because they are standardizing the interface for you. It just saves you a great deal of work.

Why the fuck would it complexify the project? If you need a push server then you need a push server. That's like saying that you should only create static pages and upload the HTML manually because adding a DBMS would complexify it and use up additional system resources. Besides, what do you think take up more resources? A daemon running in the background on the server ONLY transferring data to the client when it's needed, or having the client query the server every X seconds to check if there is something new and thereby create unneeded connections?

Do you even know what you're talking about? If you don't want to query the server constantly, then write a push server so it can send the requests to the client if there is any new information the connected client must know about.

This user is banned so there is no point in continuing this topic. I'll just lock it.

While not it's not a tutorial, this might be useful: http://framework.zend.com/manual/en/zend.ldap.html You don't have to use the framework. You can just take out individual components of it if you wish.

As far as I know, there is no official standard.

lol why not? there's plenty of "free legal advice" type places on the internet. In court: But... some dude on the internet told me!

You should encrypt the connection whenever confidential data is being transmitted. This could be user login information, credit card information, etc. You could also opt to encrypt all connections. You must be aware that you need a dedicated IP address for your certificate if you need to use it across various subdomains then you'll need a wildcard certificate.

On a static HTML file on my VPS I received the following response headers: HTTP/1.1 200 OK Date: Sun, 22 Jun 2008 21:53:36 GMT Server: Apache/2.2.3 (Debian) DAV/2 SVN/1.4.2 PHP/5.2.0-8+etch11 mod_ssl/2.2.3 OpenSSL/0.9.8c Last-Modified: Thu, 19 Jun 2008 09:44:58 GMT ETag: "7a8aec-21a-d48c5a80" Accept-Ranges: bytes Content-Length: 538 Content-Type: text/html; charset=UTF-8 Note that the Last-Modified header was set to when I actually last modified it. Apache determines this by the last change time of the file.