Newest Iteration of HTML5

HTML5 HTML 5 is the newest iteration of HTML, the basic language of the Web. HTML 5 will replace both current versions, HTML 4. 01 and XHTML 1. 0 and DOM Level 2 HTML     Before discussing HTML 5, you should be familiar with the basics of how to write HTML code. HTML is very easy to get the hang of, and once you’re excellent with writing code in standards-compliant XHTML and also find the new features of HTML 5 to be very easy to implement. Html5 defines the 5 major revision of core language of the world wide web. html5 is combination of new features are introduces for helping to web authors. New features are adding based on research authority practices special thing was defining clear. In rich internet application to reduce the need for property plug. Example of ria is adobe flash and Microsoft Silverlight the rules and regulations of w3c time table html5 will reach the standards by late 2010 . html5 is coming with a lot of new attributes and elements for using the modern web service. it also perform web form 2. 0. Html5 specifies scripting programming interfaces.

Such as     Drag and drop Timed media play back Document editing Cross document managing Micro data Browser history management. HTML 5 makes familiar lot of the coding practices that were used in earlier versions of HTML… It aims to reduce the need for proprietary plug-in-based rich internet application (RIA) technologies such as Adobe Flash, Microsoft Silverlight, and Sun JavaFX. HTML 5 also simplifies code by getting rid of elements that have fallen out of use or proved to be unhelpful. Because of an array of browser problems, frames will no longer be allowed, and because style sheets handle style better than HTML tags, “presentational” tags like ;font;, ;centre; and ;strike; will no longer be valid. WS-Security A flexible and feature-rich extension to SOAP to apply security to Web services is WS-Security (Web Services Security, short WSS). This was published by OASIS and it is a member of the WS-* family of web service specifications. Three main mechanisms are described by WS-Security: * How to sign SOAP messages to assure integrity. Signed messages provide also non-repudiation. * How to encrypt SOAP messages to assure confidentiality. * How to attach security tokens. A variety of signature formats, encryptions algorithms and multiple trust domains is allowed by this specification, and is open to various security token models, such as: * X. 09 certificates * Kerberos tickets * UserID/Password credentials * SAML-Assertion * Custom defined token The security features in the header of a SOAP message, working in the application layer was incorporated by WS-Security. To accommodate a wide variety of security models and security technologies this specification can be used in conjunction with other Web service extensions and higher-level application-specific protocols. The typical SOAP use case with a communication between trusted peers (using HTTPS) does not need WS-Security at all. It is described in Alternative, and reduces complexity and improves performance. If a SOAP intermediary is required, and the intermediary is not or less trusted, messages need to be signed and optionally encrypted.

This might be the case of an application level proxy at a network perimeter that will terminate TCP connections. The standard method for non-repudiation is to write transactions to an audit trail that is subject to specific security safeguards.

However, if the audit trail is not sufficient, digital signatures may provide a better method to enforce non-repudiation. WS-Security can provide this. lthough almost all SOAP services implement HTTP bindings, in theory other bindings such as JMS or SMTP could be used; in this case end-to-end security would be required. Even if the web service relies upon transport layer security, it might be required for the service to know about the end user, if the service is relayed by a (HTTP-) reverse proxy. A WSS-header could be used to convey the end user’s token, vouched for by the reverse proxy. Issues * If end-to-end security is required, a protocol like WS-SecureConversation may reduce the overhead. The merging of several XML-schemata like SOAP, SAML, XML ENC, XML SIG might cause dependencies on different versions of library functions like canonicalization and parsing, that are difficult to manage in an application server.

Performance WS-Security adds significant overhead to SOAP-processing due to the increased size of the message on the wire, XML and cryptographic processing, requiring faster CPUs and more memory and bandwidth. An evaluation in 2005 [1] measured 25 types of SOAP messages of different size and complexity processed by WSS4J with both WS-Security and WS-Secure Conversation on a Pentium 4/2,8 GHz CPU. Some findings were: * Encryption was faster than signing * Encryption and signing together were 2-7 times slower than signing alone and produced significantly bigger documents. * Depending on the type of message, WS-Secure Conversation either made no difference or reduced processing time by half in the best case. * It took less than 10 milliseconds to sign or encrypt up to an array of 100 kilo bytes, but it took about 100~200 to perform the security operations for SOAP. Alternative In point-to-point situations confidentiality and data integrity can also be enforced on Web services through the use of Transport Layer Security (TLS), for example, by sending messages over https. WS-Security however addresses the wider problem of maintaining integrity and confidentiality of messages until after a message was sent from the originating node, providing so called end to end security. Applying TLS can significantly reduce the overhead involved by removing the need to encode keys and message signatures into XML before sending. A challenge in using TLS would be if messages needed to go through an application level proxy server, as it would need to be able to see the request for routing. In such an example, the server would see the request coming from the proxy, not the client; this could be worked around by having the proxy have a copy of the client’s key and certificate, or by having a signing certificate trusted by the server, with which it could generate a key/certificate pair matching those of the client. However, as the proxy is operating on the message, it does not ensure end-to-end security, but only ensures point-to-point security. Web design best practices The WWW is a network of computers all over the world. The WWW is also called the Web. The computers on the Web communicate using standard protocols and languages. The W3C (The World Wide Web Consortium) are making the rules and standards for the Web. Generally we   found that some web sites are fairly easy to use while others look difficult or just plain annoying.

What makes the difference of good and the bad? Including your personal preferences, your web site should be designed to appeal to your target audience — the people who will use your web site. They may be teens, shoppers, college students, young couples etc. Beginners design web sites that work great on their own computers but may not work well on target audience. We have to remember some points for Smart and Successful Web-development: a. Develop your own ideas in your own style. b. Avoid ambiguity and be clear c. Never compromise in principles d. Support the project e. Respect the standards and target audience. Write your pages for multiple types of Web browsers–to provide trouble-free access to the widest possible audience. The World Wide Web is a multi-platform, non-browser specific medium. It is not important matter whether people browse your Web pages using Netscape, Explorer, Opera, Lynx, WebTV, Net Phonic’s Web-On-Call, Mobile Telephones, or Personal Digital Assistants. Each browser ought to render your informational Web pages without problems. If a Web page is designed properly, blind individuals, or anyone using text-to-voice or Braille displays, can easily listen to and review your work.

Run Web pages through a valuator to test their compliance with common HTML (Hypertext Mark-up Language) specifications. Modify pages until they validate, because compliant pages have a better chance of being rendered by various Web browsers, as the writer intends. However, if you intend something that is impractical with HTML, it will be no less impractical for being syntactically valid. Work with the strengths of HTML rather than trying to batter it into a WYSIWYG page design system Cloud computing Cloud computing is a technology used to access service offered on the internet cloud. Everything an information system has to offer is provided by service so users can access that services available on the “internet cloud” without has any known-how on managing the resource involved. The term cloud is used a metaphor for internet cloud computing generally combinations are as follows Infra structure as service, Plat form as a service, Software as a service cloud computing is different with grid, utility, of computing. CLOUD ANTONY: There are three types of services mainly in cloud Antony there are application services are like gmail pay roll second one is platform services are like middle wave, managing, third one is infrastructure services like amazon. Cloud computing types: there are three types of cloud computing public clouds, private clouds, hybrid clouds.

Public clouds: these clouds are used by general public the firewall already exists and the vendor having availability to fully hosted and managed. Now a days public clouds are large scale infrastructure and retail bases. Dynamically public clouds update the elements with effect the business.

Private clouds:   private clouds are only with limited organisation. When private cloud are compare to the public only operating cost is reduced. And managed by enter prize only. Organisation is more secure.

Private clouds investment and cost might be exceed public clouds. Cloud computing architecture: There are five types of layers in cloud computing. The primary layer clients in this layer different types of clients in organization having set separate computing. Second layer is services wt type of services needs to the clients and applications for adding some items or removing these things happening in application layer development. The entire thing of date is stored in this layer. layers Conclusion In my overall report i explained html5, cloud computing, security and scalability in website and web best practice. After the research i came to know that everything is linked with each other for the developing a better website.

References https://www. ehow. com/way_5368790_html-tutorial. html#ixzz0qW64UULj “When will HTML5 be finished? “. WHATWG. WHATWG Wiki. Retrieved 2009-09-10. https://www. html5reference. com/tutorial/index. pdf https://www. ehow. com/way_5368790_html-tutorial. html H^ “[whatwg] WHAT open mailing list announcement”. Lists. whatwg. org. Retrieved 2010-03-04. “HTML 5: A vocabulary and associated APIs for HTML and XHTML. “. World Wide Web Consortium. Retrieved 2009-01-28. “HTML 5: A vocabulary and associated APIs for HTML and XHTML (Editor’s Draft). “. World Wide Web Consortium. Retrieved 2010-04- ^ “When will HTML5 be finished? “. WHATWG. WHATWG Wiki.

Retrieved 2009-09-10 . ^ “HTML Working Group”. W3. org. Retrieved 2010-03-04.  “HTML 5”. W3. org. 2009-08-25. Retrieved 2010-03-04. ^ “[whatwg] HTML5 at Last Call (at the WHATWG)” ^ Hongbin Liu, Shrideep Pallickara, Geoffrey Fox: Performance of Web Services Security ^ Francois Lascelles, Aaron Flint: WS Security Performance. Secure Conversation versus the X509 Profile Retrieved from “https://en. wikipedia. org/wiki/WS-Security” Categories: Web service specifications | Computer security software | XML-based standards | End-to-end security Hidden categories: All articles with unsourced statements | Articles with unsourced statements from January 2010 https://blogs. dnet. com/Hinchcliffe/? p=488;tag=btxcsim https://blogs. zdnet. com/Howlett/? p=558;tag=btxcsim https://blogs. zdnet. com/BTL/? p=9560;tag=btxcsim https://www. businessweek. com/technology/content/aug2008/tc2008082_445669_page_3. htm https://www. ibm. com/developerworks/websphere/techjournal/0904_amrhein/0904_amrhein. html https://cloudcomputing. sys-con. com/ https://www. masternewmedia. org/news/2006/03/25/web_design_and_development_top. htm https://webdevfoundations. net/5e/chapter5. html https://www. w3schools. com/web/default. asp

Cite this page