What is the difference between Web Application and Client/Server Application?
92838
to get data through webapplication, you have to proceed generally as a three tier system in which you first access a webserver through your system ,after that you get permission from webserver,you can access mainserver through webserver based on the policies of the webserver.in simple words if you are signing up in yahoo first you have to fill an online form(this form is evaluated by webserver) \nbut in client/server you are a client of main server so you can directly access data from server if you are autherised to do that,i.e  it is generally two tier system
340175
When you say 'POST', I assume you meant the HTTP POST, instead of GET method.\nThere are many ways you can do this, and it all depends on what sort of programming you are doing?\nIs it just a simple HTML page that will send some data to the server using HTML Form? If so, you can simply add an HTML form tag with method post. e.g:\n<form action="http://xyx.com/cgi-bin/abc.pl" method="post">\n\nOr if it is not an HTML page, then you can use some programming language to create the client application. Java, VB, etc have the library (APIs) that support creating HTTP connection and sending data using POST method.
111185
Client side scripting the processing is done on the clients computer meaning it uses their cpu. Example would be javascript. Server side means it is done on the server or webserver and the results are brought back and displayed for you.  An example would be PHP.
14122
So, compared to regular HTML forms applications, they can write much more robust client applications.  They can also save bandwidth since content delivery is limited to the few changes a client requests, instead of entire pages.  The principles of AJAX lend themselves well to segmenting applications, potentially reducing server demand, and improving performance.\n\nSince most of the business rules are executed on the server anyway there's not a whole ton of "risk" - their "core" code is protected on the server.  If done right, the client-side code simply deals with delivering/presenting client content.\n\nThe tradeoffs are well worth the perceived "risks" in areas like content management, release coordination, availablility, scalability, etc., since they gain the advantage of a well-performing web-based client with a service-oriented back-end.
481397
though i am not able to under stand what u r trying to say but probably u r talking about windows forms...The forms developed in a windows application in .net are called Windows Forms...and in ASP .Net the forms are called Web Forms...If u r new i must tell u that there are two types of applications (there are other types also) Windows & Web...in Windows application u create Windows Forms & in Web application u create Web Forms
23439
Asynchronous JAvaScript and XML) Using an enhancement in JavaScript that allows Web pages to be more interactive and behave like local applications, which are also known as "rich client" applications. AJAX allows the Web page to retrieve small amounts of data from the server without reloading the entire page.\n\nPrior to AJAX, any retrieval of data from the server required that the entire Web page be refreshed in the user's computer. As a result, systems were often designed with less interaction; for example, to have the user submit a form only at the end, after all fields were filled in. In contrast, AJAX systems can validate one or two items at a time "behind the scenes" without making the session cumbersome, especially over slow connections. AJAX, also known as "remote scripting," allows Web-based applications to be designed like LAN-based applications.
280310
The code is usually divided into 2parts : client side and server side. If you use the view source option what you'll get to see is the client side scripts and some of that is also generated by the server side scripts. To get the server side scripts you'll have to ask the developers for it.\n\nHope this answers your question
417341
Simply, accessing a database through a Client-Side scripting language like JavaScript is IMPOSSIBLE. The reason is obvious, users must not be able to view the source code of the program. If you were able to access a database using a client-side scripting language, then users would be able to view the source, because the source code must be transfered to the user's computer to be interpretted.\nMany Server-Side scripting languages are listed above, ASP, PHP, JSP, Perl, etc. You have to use one of them on your server and design a Server-Side web application to access your database.\nHope it helps...
402220
Well, if I were you I would save the web application that I am making in the root folder that is available in the Tomcat folder. On running the tomcat server the page will automatically be displayed. Try it out. Oh by the way, make a folder of yours inside this root folder and then type the following in the address bar:\nhttp://localhost:8080/folder\nPls note that the port can change. Also the folder name is not case sensitive. Take care and all the best!
18055
AJAX refers to the combined use of a number of techniques to build highly-interactive Web applications.  JSON-RPC is a convention (and library) for transferring data into an AJAX application.  Thus, AJAX applications can use JSON-RPC to interact with the server.\n\nYour question implies that JSON-RPC and AJAX are somehow alternatives, which is not the case.  This confusion, in turn, suggests that perhaps you should let your contractor figure out how to best implement your Web application.
57144
Web application development in .NET with ASP.NET has evolved a great deal. The overall architecture of web applications in .Net is much more improved and robust. The enhanced features in ASP.NET make it the best available technology for web application development. The code behind the ASP.Net scripts can be in written in any .Net compliant programming language. \n\nThe script (ASP.NET scripts), logic (code behind) and presentation (view) are separated from each other so they may evolve independently. There are much more server controls now available in .Net including the standard calendar and amazingly useful data grid controls. The ASP.Net web applications can now use .NET assemblies and COM components to serve the client requests. ASP.NET pages are now compiled contrary to the ASP pages which are interpreted by the ISA server. Truly speaking, there is no comparison between ASP and ASP.NET... ASP.NET simply rules!
81287
In simple terms: \n\nA server is a powerful computer that serves, i.e. performs some sort of task, for other, usually smaller, computers attached to it via cables or phone lines. These smaller computers are called clients.\n\nHere's an example: When you're at home browing the web, your computer, or to be picky your browser software, is the client and it connects to a server via your phone line. When you want to view a web page or download a file, your computer (client) contacts the server and asks it to fetch the page or file and send it back to you. Simple.
718372
running javascript on client-side is great because the server is exempted for all the work such as validation etc. Infact in Oreilly's cookbook for javascript you will find code for client side search where the server just sends the client relevant site database from which the client can search through using the script...
981119
ASP = Active Server Pages.  the code you place in these pages is a mixture of front end javascript+HTML/XML and back end VBscript/.NET code.\n\n There is no actual code (except your javascript, or generated javascript) that gets pushed to the web browser.  Early ActiveX solutions sent an executable to the browser, but these are no longer used in modern development - unless it is a large bundle of extra browser capability (like Adobe Reader, Flash/Shockwave plugins, etc)\n\n You ASP or ASP.NET code runs on the server via an IIS-controlled service. It is not visible, and cannot be pirated by anyone outside your firewall (the web clients).  If you are saying your code is be hacked off this server, your security hole lies in the configuration of your network and IIS server, not in your programming paradigm.\n\n That said, use safe coding practices.  Read and understand how to configure your web server, and obey the rules of never using usernames/passwords or other private network information from within your javascript or HTML layers.  If you're writing with ASP.NET (highly recommended) then most of these things are taken care of, except for the locking down of your network.  That you have to do outside of whatever sites you're publishing.\n\nYour LAN may be giving people access to your IIS machine.  If this is the case, turn off the guest account and all other accounts for that machine.  Do not develop on that machine, but simply on your own machine, then install the application when you're finished (prevents attacks from folks who know how to attach a debugger using the frontpage extensions to your IIS).  On the IIS machine, save just one login for installing, and use anonymous access for to web site.  Hope this helps.
1178445
Hi there,\n\nFrontend - Which Visible to End User like Forms , Presentation, Graphs, Menus, Reports etc\n\n( VB, VB.net, VC++, Delphi - Frontend tools ) \n\nBackend - Not visible to end user , internal process and storage like Assembly, DBMS like Oracle, SQL Server, MYSQL etc.\n\nHope its little bit clear to you now .. \n\nCheers
394120
the client connects to the server and gets all the info it needs...\n\nthe client is the users machine
192670
Most people think of it as software with a web-browser\ninterface and server-based computations.\n\nThere can be variations on that theme in that the UI\nmight be client-based Java or javascript (so that some\nof the computations are performed on the client).  But\nthe important distinction is that the user doesn't \nhave to buy/load/administer any client-side software.