This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
i am agree with Dave the correct answer are A and C this part from RAMU MEDA notes HTTPS �Stateful / connection-based. �Web protocol developed by Netscape and built into its browser that encrypts and decrypts user page requests as well as the pages that are returned by the Web server. �HTTPS is really just the use of Netscape's Secure Socket Layer (SSL) as a sublayer under its regular HTTP application layer. �HTTPS uses default port 443 instead of HTTP port 80 in its interactions with the lower layer, TCP/IP. �SSL uses a 40 or 128-bit key size for the RC4 stream encryption algorithm, which is considered an adequate degree of encryption for commercial exchange. �URL that starts with https://. When you click "Send," to send the page back to the catalog retailer, your browser's HTTPS layer will encrypt it. The acknowledgement you receive from the server will also travel in encrypted form, arrive with an https:// URL, and be decrypted for you by your browser's HTTPS sublayer �HTTPS and SSL support the use of X.509 digital certificates from the server so that, if necessary, a user can authenticate the sender. �SSL is an open, nonproprietary protocol that Netscape has proposed as a standard to the World Wide Consortium (W3C). �HTTPS is not to be confused with SHTTP, a security-enhanced version of HTTP developed and proposed as a standard by EIT. �Pros: osecure � only �in-the-clear� at client / server oallowed through firewalls (most of the time) owidely supported / deployed �Cons: ocomputationally expensive � excluding dedicated hardware, HTTPS can only process 10% of the traffic HTTP can olow performance compared to HTTP oAdmin overhead � renewing certs, etc. �Each party (client/server) may hold multiple SSL sessions. �Each session may include multiple secure connections.
[ May 07, 2006: Message edited by: Usama Rashwan ]
SCJP2, SCWCD , SCEA Part I<br />Enterprise Application Development with IBM WebSphere Studio, V5.0<br />IBM Certified Solution Developer - WebSphere Studio, V5.0<br />IBM 483 (Enterprise Connectivity with J2EE)<br />IBM Certified Specialist - IBM WebSphere Application Server, Advanced Single Server Edition for Multiplatforms, V4.0
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com