Consuming Web services through Delphi
Blog Posted By: Anil Choudary
Evolution of the web industry leads developers through sophisticated technologies waving and balancing between client-oriented and server-oriented approaches. New standards for browsers, protocols, and scripting languages replace each other. The next step is XML - extended markup language, which suppose to replace HTML and dominate in web applications as main communication format. XML has been designed to transfer data to clients separately from data's format. Web server or Internet client should combine XML data with a style sheet and generate well-known HTML code to display the data.
On the other hand you may use XML language to extend functionality of your programs. Consider XML as a universal data storage format, which as a matter of fact much more flexible than DBF or any other relational database format.
Why should you use XML as the only advanced way to create web pages? XML is more universal and more flexible than just only markup language. You may even create your own data format or network protocol by inventing your own tags and interface.
Below you will find one example of such non-standard XML usage, designed for use in Borland Delphi applications.
Microsoft Live Labs Volta - something similar to GWT
Blog Posted By: Anirban Ganguly
Developers can target either web browsers or the CLR as clients and Volta handles the complexities of tier-splitting for you. Volta comprises tools such as end-to-end profiling to make architectural refactoring and optimization simple and quick. In effect, Volta offers a best-effort experience in multiple environments without any changes to the application.
Exception Handling in EJB – A walk through
Blog Posted By: S Abdul Razack
As J2EE has become the enterprise development platform of choice, more and more J2EE-based applications are going into production. One important component of the J2EE platform is the Enterprise JavaBeans (EJB) API. Together, J2EE and EJB technology offer many advantages, but with these advantages come new challenges. In particular, any problem in an enterprise system must be resolved quickly. In this blog, we discuss best practices in EJB exception handling for faster problem resolution.
Exception handling is simple enough in a hello-world scenario. Whenever you encounter an exception in a method, you catch the exception and print the stack trace or declare the method to throw the exception. Unfortunately, this approach isn't sufficient to handle the types of exceptions that arise in the real world. In a production system, when an exception is thrown it's likely that the end user is unable to process his or her request. When such an exception occurs, the end user normally expects the following:
A clear message indicating that an error has occurred
· A unique error number that he can use upon accessing a readily available
customer support system
- Quick resolution of the problem, and the assurance that his request has been processed, or will be processed within a set time frame
Software Quality Assurance - Means of monitoring the software engineering processes.
Blog Posted By: Rani Agasti
Software quality assurance (SQA) consists of a means of monitoring the software engineering processes and methods used to ensure quality. It does this by means of audits of the quality management system under which the software system is created. These audits are backed by one or more standards, usually ISO 9000 or CMMI.
It is distinct from software quality control which includes reviewing requirements documents, and software testing. SQA encompasses the entire software development process, which includes processes such as software design, coding, source code control, code reviews, change management, configuration management, and release management. Whereas software quality control is a control of products, software quality assurance is a control of processes.
Software quality assurance is related to the practice of quality assurance in product manufacturing. Therefore its function, benefit and costs are not as easily measured. What's more, when a manufactured product rolls off the assembly line, it is essentially a complete, finished product, whereas software is never finished. Software lives, grows, evolves, and metamorphoses, unlike its tangible counterparts. Therefore, the processes and methods to manage, monitor, and measure its ongoing quality are as fluid and sometimes elusive as are the defects that they are meant to keep in check.
Marketing today isn't about talking at customers and prospects
Blog Posted By: Jithesh Nair
B2B marketing needs to become more personal. Facebook is already atomizing into many mini-Facebooks focused on narrowly defined special interest groups.
Indeed, today, the cold call is going the way of the shivering dinosaur. Providers who truly understand customers’ business and IT requirements and have done their homework have chance.
B2B marketers have a very high standard of communication that they have to impart. We know the services that we're selling; we know the need for those things in the external marketplace. Marketing today isn't about talking at customers and prospects; it's about creating and engaging with communities. Within the next couple of years, I believe that everyone is going to belong to a mix of different online communities. One person could belong to a religious community, a community for people with diabetes etc..