Shrikant Wagh's Blog

Build 255 Commission Report

PodShow Inc, San Francisco, 12/13/2007 : PodShow successfully pushed, a much awaited, build 255 to production today. This build has refractored collections & channels, media shard and updated external feeds. This platform update will lay a foundation for PodShow's strategic development of Weapons of Mass Entertainment [WOME]. PodShow's ability to build any form of WOME on very short duration is feared by many governments and organizations across world. PodShow, Inc. has been labeled as one of the extremist entertainment organization by Bush government, especially when President Bush himself feels threatened by PodShow. As Bush claimed himself to be the biggest clown of the world and President Bush want to retain his world dominance in entertaining people of the world by his stupendous acts. After thorough interrogations of key members of Engineering, OPS, Product team and water-boarding of QA team at PodShow, NIC [National Intelligence Commission] revealed the fact today that a PodShow Rebel, Mr. Erik Vanbragt [alias "the Dutch"] and some key members of Engineering, OPS and QA team, played a very significant role in development of this technology and making it accessible to all WOME users across world on 12/13/2007. During this trying period, some unidentified organization had tried to eliminate one of the key developer of this technology - Mr. Dutch, by knocking him of his bike in San Francisco on his way back home form his secret workplace. In another assassination attempt he was targeted by bionic weapons which gave him flu for couple of days. But all of these attempts on his life did not deter Mr. Dutch from performing his duties. Though Build 255 commission stated in the investigation reports that Mr. Dutch fixed all those issues himself, White house continue to believe that Bin Laden, Al Qaeda and other entertaintment extrimist organizations had helped him in pursuing this act as it was un-seemingly difficult for one person to carry out such a humongous tasks.

Mr. Dutch also been known to have links with some  undisclosed entertainment extrimist organizations in eastern Europe. Phone taps and skype surveillance records indicated that many conversation originated to and from these countries. APP [Associated Press of PodShow] reported that other like minded organizations helped Mr. Dutch with quashing the bugs and with all of their arsenals to execute this task. He was also helped by other rebels in his organization. "All folks at PodShow are so foucused on dominating the world by their WOME and the commitment to the cause by these individuals will shame many assasination squads and suicide bombers across unvierse", said Mr. Anton - trainer of the PodShow assasination squad. A phone messages to the leader of these rebellions and WOME development team Mr. Eyal Shavit went unanswered. He was believed to be out of town defining PodShow future attack strategies and raising funds to sponsor the extremists activities for the organization. CIA, NSA and homeland security totally denounce the torture and water-boarding of PodShow QA team during this interrogations. The video tapes of these interrogations were supposedly destroyed. In a separate press conference Condi issued a statement that White House is very firm about their beliefs and did not ruled out the possibility of terrorist organization helping Podshow build WOME [Weapons of Mass Entertainment]. She will advise Mr. Bush to continue to be vigilant without dropping his pants. "Extremist organization like Podshow cannot be taken lightly, especially when they are building a very advanced, kick-ass WOME [Weapon of Mass Entertainment]. If successful these guys can kill billions with laughters", Miss Rice quoted. When Mr. Bush was confronted with these allegations made by White House. President Bush was very quick to rebuff those with big fart. "F**k NIC, F**k CIA, F**k NSA, F**k my security council and my advisers!!! Bush said, "Bitches!!! Trying to screw me off again with another false intelligence report". Mr. President congratulated Mr. Dutch and PodShow WOME team by sending the inimated message.

Web Services Interoperability and Performance Best Practices - Part 2  By - Shrikant Wagh

Best Practices to Improve Web Services Performance

• Design your Web service interface to minimize the network traffic. A 'coarse-grained' API is better, as you minimize the number of requests a client has to make to get information.
• Large SOAP messages are a performance bottleneck due to time spent parsing them. Keep your payload size as small as possible
• Complex SOAP message are a performance bottleneck due to time spent serializing/deserializing messages. Keep your payload complexity low. However, payload complexity and payload size are often design tradeoffs.
• SOAP intermediaries (gateways, proxies) should minimize parsing of messages.
• Better XML parsing techniques. For most applications, event driven parsers (SAX style) are more performant than DOM style parsers.
• Security has performance costs. Not all SOAP traffic needs to be secure. The performance costs of an end-to-end security (i.e. WS-Security) is, in most cases, higher than a transport level security mechanism like SSL.
• Caching is a way to improve performance for processor-intensive services, though this is applicable only for read-only type of services.
• Many of the performance best practices for web applications will apply here too (using EJBs v/s JavaBeans, passing-by-reference of EJB components, Hardware and capacity settings, JVM setting etc.)
• Persistent connections are good for performance in case of a large number of messages of small payload size. For larger messages, this has less of an effect. HTTP keep-alive is way to request that a HTTP connection persist, though this is a default in HTTP/1.1.
• Streaming connections are good for performance in case of a large payload size. HTTP 'chunked encoding' is a kind of streaming, and is supported by HTTP/1.1.
• Binary encoding of some payload elements should be considered.
• The larger the message, the longer the time required to parse it.
• Marshalling and un-marshalling of Objects to XML and XML to Objects. The more complex the structure of a message, the longer the time required to map between programming objects and XML elements.
• Processing of WS-Security capability that includes XML Digital Signatures and XML Encryption. Security between application end points isn't free and can add surprisingly long latency to the processing of service requests.

Best Practices for Web Services Interoperability

• Design the XSD and WSDL first, and program against the schema and interface.

• If at all possible, avoid using the RPC/encoded style.

• Wrap any weakly-typed collection objects with simple arrays of concrete types as the signature for Web service methods.

• Avoid passing an array with null elements between Web services clients and servers.

• Do not expose unsigned numerical data types in Web services methods. Consider creating wrapper methods to expose and transmit the data types.

• Take care when mapping XSD types to a value type in one language and to a reference type in another. Define a complex type to wrap the value type and set the complex type to be null to indicate a null value.

• Because base URIs are not well-defined in WSDL documents, avoid using relative URI references in namespace declarations.

• To avoid conflicts resulting from different naming conventions among vendors, qualify each Web service with a unique domain name. Some tools offer custom mapping of namespaces to packages or provide refactoring of package names to resolve this problem.

• Develop a comprehensive test suite for Web Services Interoperability Organization (WS-I) conformance verification.

• Using vendor tools to derive the Web services semantics in WSDL from implementation code is convenient, but this approach ignores the design of the message schemas which is central to Web services interoperability in heterogeneous environments (J2EE technology versus .NET, for example).

• Different naming conventions in .NET and Java technology can result in namespace conflicts, as can the use of relative URI references.