毕业设计我帮你

PHP.NET正式版开发者指南
介绍：
随着PHP.net的发展，我们可以看到从传统写稿到全功能在线编程转变的开始。VBScript再不是唯一的选择, 因为程序员现在可以用PHP.net中内部组件，来发挥Visual Basic(VB)和C的全部功能。
不可否认.NET普遍被开发者所接受。它已经证明它自己是一个关于编程世界怎样改变的框架。它使任何人能够用与框架相容的任何语言编码的一个软件解决最小Theintroduction办法
在这章里，我们将看一下服务器页(PHP)它自己开始多年以前，从他开始迷惑程序员开始，当然它有一些问题，但，.NET结构是解救其他编程问题的方法。PHP 怎样与服务器和客户合作会有一些改变，以便为用户提供你想要提供的信息。
即使这是稳定的比特，并且很多人已经以为我们正在比特2的内部基本上看到的是“冰冻”的特征，但由于比特的自然属性，他仍有一些创新。在框架内学习这些问题能对它所存在的问题坐准备。
从PHP的历史开始学习：
PHP的历史可以追溯到1995年，那时微软公司意识到他们通过不包括因特网正在工业方面的基本的变化里落后。直到微软公司点一直发展他们的专利技术，工具和微软公司网络的网络协议，突然之间他们需要一个因特网策略。
随着ie浏览器在浏览器市场的飞速发展和在1000家最有财富的公司里安装网络信息服务，微软公司已从原来的瓶茎中走出来了。
PHP的起源：
回到90年代中期，当时商业的网络化还不成熟，要想网络成为做生意的主要场所，网络开发者可选择的工具还不是很多。在选择服务器编程平台和桌面开发工具遇到的阻碍还没有很好的解救方法，最后，程序员使用编程语言（如：c，delphi，visual basic）也无法解决网关接口中出现的问题，或解释编程预言perl和rexx在unix系统中的用做问题。
在1996年初，微软公司在网络信息服务上有了第一个包括因特网信息服务在内的因特网信息服务编程接口（ISAPI）。ISAPI其实就是Windows Win32 API的延长。它作为创造Web 服务器与因特网信息服务器的内部运转相互作用的软件发展起来，并且在功能上带来了5倍的曾加。除了你想到的性能曾加，它也带来了一些阻碍程序员发展的负面影响。因此，我们应公平对待（ISAPI）在编程方面带来的重大革命。所以，微软鼓励开发者运用他们的技术，通过ISAPI，建立起一条通过数据库连接（ODBC）把因特网数据库连接器与返回的数据结合在一起的新路。
ISAPI和IDC 技术第一次作为一个基本的交互式应用服务器平台还不成熟并且没有得到网络服务器的验证。
但是，其它此类产品却很受欢迎，如Netscape Livewire。Livewire是在Netscape 的Web 服务器下运行并且使用一个页逻辑的Java脚本的版本，以及使用Java 组成部分的一项技术。令人遗憾是，Livewire与ISAPI存在相同的制约，就是其在网络服务停止和开始阶段还有带完成。
PHP的必须性
因为不是所有的网络开发者有能力编写ISAPI内的程序，并且因为ISAPI需要计划和编辑，会在发展一个基于ISAPI项目上使生产速度降低，因此，初学者和中间程序员发现需要学习一种工业化的编程语言，如C++那样，以解决把简单的编程页面嵌如到*.dll文件时所遇到的阻碍。
Visual Basic程序，虽然容易发展，但当用于CGI时，不好执行，也不宜慑取资源。其它语言象perl语言要求Web 服务器启动一个不同的命令行程序解释并且执行被请求的数据，这就增加页装入时间并且降低的服务器性能。CGI会运用自己的资源强迫网络服务器不运行新的程序或通过此服务器的程序。这不但费时而且会用完宝贵的RAM。
90年代摆在开发者面前的另一个问题是当时网站是一种html语言和逻辑语言的混合实体。他们需要一种方法使程序员的代码与设计者的页版面编排HTML 和设计混合在一起，而且使其中一个不与其它的产生混乱。有很多解决这个问题的方法，从传统的模版切换中我们知道，服务器执行代码基于特别的HTML。数据库驱动的交互性是另一项挑战。对复杂的网站的需求刚刚开始， 开发者应需要容易管理方式，可提供的工具不能使这一任务变得容易。但是，能完成任务的就可以获得与困难相匹配的奖金。
那什么才是其他人所需要的解决方按呢。首先，它需要成为象Perl一样的简单的按稿子的，基于文本的技术，因此，开发者运用简单的工具且不复杂的改变他们的网页。并且，它需要在保持高性能时有效降低资源要求，因此它需要被放在如ISAPI一样的服务器环境内执行，但是没有其那么复杂。设计者和纪律严格的小组要求，它应该包括SSI 模板特征使布局结合的页面在管理上简单化。为了其能够真的流行，它必须对一个开发者和一个团体而言，是一种容易上手的语言。进入动态网络服务。
为什么PHP 最初没被含盖：
活跃的服务器页不是很快就取得成功的。虽然它确实对一个大的团体是容易理解的，但这些人是已经精通Visual Basic编程或者Visual Basic。而那些没有在Visual Basic上花费更多精力的，必须提高他们在Visual Basic方面的知识，以避免在运行中出错。错误包括不良的记忆管理， 缺乏坚固的线管理能力，例如正规表达式。因此，当与有Perl的CGI相比时，PHP就显得有些不足。
在那时， 因特网信息服务器还处在初期，并且效率很低，尽管微软的公共关系和人员在努力地使这种状况扭转。PHP在与时下流行的软件比起来还显得还比较弱，但还是被完成了。
直到1997年，网络编程才能很好的容入CGI和perl中去。高性能的网站通常是c语言编程和perl形式处理的有效结合。
围绕微软在因特网方面的努力有很多怀疑，包括IIS 和IE浏览器。而且，ISAPI在很多人的帮助下也没有得到完善。但是，在这种不确定的情况下，微软公司看见很多Windows NT 4 许可证特别适合网站建设和发展，第三方在除了小的组成部分以外其他任何事情的支持都不够充分，但是，就象微软的其它产品一样，即产品在上市后，证明他们是对的，PHP也不例外。
鉴于Perl还很多的开发者拥有，PHP的开发者在那时没有得到支持。Perl的程序员会吧他们的的代码分享和公开，因此得到很多支持。我们把这与根深蒂固具有竞争性和在财政上领导的第三者零部件卖主在分布因特网应用(DNA)世界和Windows内的哲学对照，就可看出。当然，如果你不喜欢PHP，这个团体就不会如此的发展起来。
PHP 1.x的发展
PHP 1.x是因特网信息服务器2的升级，它使其发展到第三个版本，并且，它被设置为一可选择下载组成部分。公众比特在1996年10月被第一次免费提供，最终的上市也是IIS在服务器市场迅速赶上Netscape的一个因素。
在相同的时期，微软公司已经购买并且更进一步开发了一个网站建设工具叫FrontPage，它给网络建设带来了一个新的概念，使开发者在没有使用文件传输协议(FTP)的条件下，部署网络应用组件。这个概念会渗入到微软公司新的可视化html和PHP编辑环境中去。
PHP 1另人吃惊的适应第一个版本。PHP包括当今程序员所带来的革命性功能，如防止程序员数据库实施与ActiveX数据对象有差别，数据容易被访问且结果正确，还有在执行读或写时混合与匹配逻辑语言的功能加强；但是，总的来说PHP 1是新鲜事物，并且很多开发者都急切的想掌握它。
PHP 2.x的发展
当PHP 1发展且已站稳脚跟，微软公司释放一个因特网信息服务器和升级PHP 的新版本，它与Windows NT绑在一起。这次，PHP被建立在一个网络安装程序上。这个网络服务器有重大改进，它在一些简单的邮件传送协议上能够更好的支持和完成其功能。
随着PHP 2的到来，开发者在解决一些方法问题的技术将成熟。很多大公司运用微软的平台来完成信息传送和技术上准备。
PHP 2在运行上实现了全面改进，例如增加的文件系统功能性，增加的组成部分和语言改进。第三方用户释放组件以填补他们在功能上的不足，并且，开发者正在用PHP 的零部件结构，制造自己的零部件。
开发者的工具也应升级，因为PHP 2改进很明显且与Visual Studio结构有效的结合，可以进入资源内部来保存资源。第三者工具卖主也有很多术士样式开发者的工具箱和整体环境来市场，例如受欢迎的Macromedia Ultradev。
近年来，微软公开了大量语言的代码，考虑到在语言方面的改进，例如对正规表达式的支持，动态网页没有特别的需要。
PHP 2带来的改变
    PHP 2为开发者提供了一个更加稳定和丰富的环境。所有的技术都经过调试和运行，并且程序员很快就会感觉此技术的稳定。这个稳定得到了确认，很多成功表明此平台不但可以安全传送，且经常升级。实际上，IIS 4被重建为一个MTS装置，PHP 和MTS实际上是可在一个环境下运行。另一个改进是与微软公司信息排队的工作。另一项改进是这允许PHP 和组成部分通过网络交流，来完成大规模的信息处理，如把电子商务系统和现有的企业资源计划(ERP)基础设施结合起来。
 
PHP.NET Developer's Guide
Introduction：
With the advent of PHP.NET we see a shift from traditional scripting to the beginning of full-fledged programming online. VBScript isn’t the only option anymore, as programmers can now employ the full power that lies behind both Visual Basic (VB) and C within their PHP.NET assemblies.
There is no denying the widespread acceptance that .NET received from the developer community. It’s proven itself to be a well-developed framework withsolid ideas on how the programming world should continue to change.Theintroduction of a software solution that enables anyone to code in any language that is compatible with the framework is groundbreaking to say the least.
In this chapter we will take a look at how Active Server Pages (PHP) itself began just a couple of years ago and how it has captivated programmers ever since. It has had some problems, of course, but the .NET architecture seems to have found solutions to many preexisting programming problems.There have also been changes with how PHP works with the server and client, to provide the user with the information that you want to provide.
Even though this is a stable beta, and many people are assuming already that what we are seeing within Beta 2 is basically the “freeze” for many features, it still has a couple of caveats, due to its beta nature. Learning from these problems within the framework can allow for preparation against it.
Learning from the History of PHP：
You can trace the history of PHP right back to 1995 and the momentous occasion when Microsoft realized they were falling behind in a fundamental shift in the industry by not embracing the Internet. Up until that point Microsoft had been developing their proprietary technologies, tools, and network protocols for the Microsoft Network; all of a sudden they needed an Internet strategy and fast.
Microsoft has gone from a position of playing catch-up to one closedominance, with the Internet Explorer Web browser having a strangle-hold on the Web browsing market, and Internet Information Server (IIS) installed at the majority of Fortune 1000 companies.
The Origins of PHP：
Back in the mid ‘90s, when the commercial Web world was still young, there wasnot a great deal of choice of tools for the Web developer who wanted to make his or her Web site a truly useful place to do business.The choices were limited in both available server-side programming platforms and also desktop development tools to produce the solutions. In the end, the programmer was stuck with clumsy Common Gateway Interface (CGI) programs using compiled languages such as C, Delphi, and Visual Basic, or interpreted scripting languages like Perl or Rexx, and operating system shell scripts on systems such as UNIX.
In early 1996 Microsoft had a first stab at improving the situation by including the Internet Server Application Programming Interface (ISAPI) technology as part of Internet Information Server. ISAPI is an extension to the Windows Win32 API. It was developed as a way to create Web server software that interacts with the inner workings of Internet Information Server, bringing what was claimed to be a five-fold increase in performance. As you can well imagine from this description, as well as the immediate performance increase, it also had a side effect of increasing the complexity of the development for the programmer. It wasn’t for the faint hearted, and it takes some serious hardcore programming knowledge to do ISAPI applications right.As well as ISAPI, Microsoft encouraged developers to embrace their Internet Database Connector (IDC) technology.This was a new way to connect Web sites to back-enddatabases through Open Database Connectivity (ODBC).
The ISAPI and IDC technologies lifted Microsoft’s youthful and as yet unproven Web server from being a glorified file server to being a basic interactive application server platform for the first time.
Other vendors had tools out there, and several were very popular, such as Netscape Livewire. Livewire was a technology that ran under Netscape’s Web server and used a version of JavaScript for page logic, and also used Java components.Unfortunately, Livewire had similar limitations to ISAPI in that it was acompiled technology and the server needed stopping and starting to make changes visible.
Why PHP Was Needed：
Not all Web developers have the programming skills needed to write ISAPI applications, and because ISAPI requires the compilation of programs, there are extra steps in producing an ISAPI-based site that slow development down. Novice and intermediate programmers found the need to learn an industrialstrength language, such as C++, and compile even the simplest of their page logic into .dll files a real barrier.
Visual Basic programs, although easier to develop, when used for CGI, performed poorly and the overhead hogged resources. Other languages such as Perl require the Web server to launch a separate command-line program to interpret and execute the requested scripts, increasing page-load time and reducing server performance. CGI itself hogs resources because every page request forces the Web servers to launch and kill new processes and communicate across these processes. This is time consuming and also uses up precious RAM.
Another problem facing development teams in the mid ‘90s was the fact that a Web site is a mixture of Hypertext Markup Language (HTML) and logic.They needed a way to mix the programmer’s code with the designer’s page-layout HTML and designs without one messing up the other.There were many solutions to this problem, ranging from custom template systems to Sever Side Include (SSI) statements that told the server to execute code based on special HTML comment tags.
Database-driven interactivity was another challenge.The demand for complex Web sites had just kicked off, and developers needed to supply that demand in a manageable fashion, but the tools available did not make this an easy task.Those who could achieve it demanded rewards that matched the difficulty of what they were being asked to do.
What was needed was a solution for the rest of us. It needed to be a simple scripted text-based technology like Perl, so developers could tweak and alter their pages without compilation and with simple text-editing tools such as Notepad. It needed to have low resource requirements while keeping high performance; therefore it needed to be executed within the server environment just like ISAPI, but without the complexity. Designers and cross-discipline teams demanded that it should include SSI and template features to make integrating page layouts simpler to manage.To be truly popular, it should run off a language that would be easy to pick up and was familiar to a large community of developers. Enter Active Server Pages!
Why PHP Was Not Originally Embraced：
Active Server Pages was not an overnight success, though understandably it did capture the imagination of a large sector of the development community, particularly those already well versed in Visual Basic programming or Visual Basic for applications scripting.
Others who did not have an investment in Visual Basic knowledge found the limitations of Visual Basic, and by extension Visual Basic Scripting, reasons to avoid the technology. Faults included poor memory management, the lack of strong string management abilities, such as Regular Expressions, found in other established languages.When compared to CGI with Perl,PHP was found lacking.
At that time, Internet Information Server was in its infancy, and take-up was low, despite Microsoft’s public relations juggernaut going into full flow after the company’s much-reported dramatic turnaround. In comparison to current versions of the software it seems very poor, but it was still competitive on performance.
Until 1997, back-end Web programming was pretty much owned by CGI and Perl. High-performance Web sites usually had a mix of C-compiled programs for the real business engine, and Perl for the more lightweight form processing.
There was a fair amount of doubt and suspicion around Microsoft’s Internet efforts, including IIS and Internet Explorer, and ISAPI had not done all that much to bring across a huge sector of the development community. Despite this uncertain atmosphere, Microsoft saw many Windows NT 4 licenses being bought specifically for Web hosting and development increasing.Third-party support for anything other than small components was initially slow, but, as with all Microsoft products, after the first couple of releases they usually get things right, and PHP was no exception.
Whereas Perl had a huge community of developers led by the heroic figure of Larry Wall, the PHP developer was not yet well supported.A Perl programmer was encouraged from the top to share and make his or her code open, so the community thrived, with every conceivable solution or library just a few clicks away at the Comprehensive Perl Archive Network (CPAN) site, or at one of the many other Web sites and news groups. Contrast this with the ingrained competitive and financially led philosophies of the third-party component vendors in the Windows Distributed Internet Applications (DNA) world. Of course, it did not take the PHP community long to grow to be the loving, sharing success it is now.
Developing PHP 1.x：
PHP 1 was an upgrade to Internet Information Server 2, bringing it up to version 3, and was installed as an optional downloaded component.The public beta was first made available in October 1996 and the final release was a factor in IIS quickly overtaking Netscape in the server market.
  Around the same period, Microsoft had purchased and further developed a Web site authoring tool called FrontPage that brought with it a new organizational and hosting concept of the FrontPage Web, enabling the developer to deploy Web applications in drag and drop style without using the File Transfer Protocol (FTP).This concept would be carried through into Microsoft Visual Interdev, Microsoft’s new HTML and PHP editing environment.
  PHP 1 was surprisingly feature-rich for a version 1 product. It included much of the revolutionary functionality PHP that today’s programmers take for granted, such as ActiveX Data Objects that shield the programmer from differences in database implementations, with record sets to easily MYSQL and navigate database query results, and the ability to mix and match logic and presentation code in the example, options for reading and writing to the file system; but overall,PHP 1 was a breath of fresh air, and many developers quickly and eagerly adopted it.
Developing PHP 2.x：
Once PHP 1 had settled and become established, Microsoft released a new version of Internet Information Server and an upgrade to PHP, with a combined download called the Windows NT 4 Option Pack.This time,PHP was built in to the Web server setup and was not seen as an extra.The Web server was a big improvement, with better support and functionality all round and the addition on a Simple Mail Transfer Protocol (SMTP) Mail service.
With PHP 2, the technology matured to the point where developers could really implement powerful, large-scale solutions. Big-name companies adopted the Microsoft platform for their high traffic transactional sites and the technology proved itself time and again against the demands of serving up millions of page views.
From launch, PHP 2 showed improvements across the board, such as increased
file system functionality, added components, and language improvements.Thirdparty developers released components into the market place that filled in every conceivable gap in functionality, and developers were producing their own bespoke components through PHP’s Component Object Model (COM)-based architecture.
Developer tools also had upgrades, with Visual Interdev becoming much improved and better integrated into the Visual Studio suite, with MYSQL to Visual Source Safe for source control.Third-party tool vendors had also developed their own solutions, with many wizard-style developers’ toolkits and integrated environments coming to market, such as the popular Macromedia Ultradev.
More recently,Microsoft extended the language code with incremental releases of the language runtime Scripting Engines, allowing for improvements in the languages, such as support for Regular Expressions, without the need for full new versions of Active Server Pages.
Major Changes with PHP 2：
Moving to Active Server Pages 2 brought the developer into a more stable and feature-rich environment. All PHPects of the technology were tuned and tweaked, and programmers really felt that things had settled into a stable technology.This newfound confidence was in part due to the evidence of successful transactional sites actually showing that the platform could deliver, but also the fact that the technology had been boosted under the hood with tighter integration with Microsoft Transaction Server (MTS). In fact, IIS 4 was rebuilt to be a MTS application, and so PHP and MTS components were actually running in the same processes. Another improvement was the work with Microsoft Message Queue.This allowed PHP and components to communicate across networks, ideal for largescale applications with complex backend requirements, for example, e-commerce systems integrating with existing legacy enterprise resource planning (ERP) infrastructures.