Posts

Showing posts from 2014

Q & A (Question with Answer)

1) What is prox & Reverse Proxies:   Web Proxies A proxy server is a gateway for users to the Web at large. Users configure the proxy in their browser settings, and all HTTP requests are routed via the proxy. Proxies are typically operated by ISPs and network administrators, and serve several purposes: for example, to speed access to the Web by caching pages fetched, so that popular pages don't have to be re-fetched for every user who views them. to enable controlled access to the web for users behind a firewall. to filter or transform web content. Reverse Proxies A reverse proxy is a gateway for servers, and enables one web server to provide content from another transparently. As with a standard proxy, a reverse proxy may serve to improve performance of the web by caching; this is a simple way to mirror a website. Loadbalancing a heavy-duty application, or protecting a vulnerable one, are other common usages.

what is design patterns? which design patterns mostly used in .net? How it is used with examples?

Guys ... i cant post all of the DP samples ..nonetheless u get it over the internet but i can just brief u bout the Design patterns 1. Design patterns are the general solutions to the design problems.... (Though they dont give you the code) 2. Design patterns show how to build systems with good OO design qualities 3. Design patterns provide a shared language that can maximize the value of ur communication with other developers The patterns that are commonly used in .NET 1.Facade -- business obj invoked by UI thru Facade 2.Composite -- Menu ctrl designed thru Composite pattern 3.Strategy -- lets the algorithm vary indep'ly from clients that use it 4.Observer -- Error logging and tracing implemented using this pattern 5.Abstract Factory -- solves the problem of accessing diff databases 6.Singleton -- one instance 7.Proxy -- Used in cases of Just in Time Loading..

WebCenter Sites VS Site Studio

WebCenter Sites VS Site Studio: What You Gain, What You Lose By: Jon Chartrand – Solution Architect There have been an increasing number of clients questioning the real differences between these two products– not just in terms of the overall picture but on a feature-by-feature basis. After all, there are tens of thousands of highly functional Site Studio websites out there today (some of which I built) and when contemplating the shift from Site Studio to WebCenter Sites the question, “What will I gain and what will I lose?” is an extremely valid one. I thought it would be a worthy exercise to line up some of the major legacy features that clients have always found important and some of the newer didn’t-know-I-wanted-that features and see how both WebCenter Sites and Site Studio stack up. Microsite Management It’s becoming fairly common in my experience that clients aren’t just building and managing a single site anymore. Trying to squeak out as much ROI as possible means utiliz

What we can/should do with website after successfull deployment:

Adobe Link Tracking: Site catalyst https://outv.omniture.com?v=ZjZXB2MjqSR72qwRXknG6HbUzjDfml1t https://outv.omniture.com?v=ZkZXB2MjqIYz6utKW7VGqtyz81XDJAWQ https://outv.omniture.com?v=ZiZXB2MjokKfYcfdtnSQjmCZsRsBsdKK  Ensighten: I.                               Overview Ensighten is implemented by deploying one line of HTML code on to pages of your web site. We recommend placing the code at the very beginning of the HEAD section of each page. The easiest and the most efficient way of deploying the code is inserting it into a template or master pages that are used for generating each page on a web site. This ensures that all pages of the web site contain the code. The HTML code is static, meaning it does not require any customization or any changes after deployment. It does not ever change and requires no variable declarations for it to function, so it will never require the modification of your site for it to function. The tag is implemented only once and does n

SharePoint 2013 - “Web Content Management Key Features”

Image
  SharePoint 2013 -           “Web Content Management Key Features” Table of Contents Introduction . 3 Content Authoring, Design, and Branding Improvements . 4 Search-Driven Publishing Model 8 Metadata and Navigation . 13 Support for Multilingual Sites . 15 Description: The Deployment Plan describes the factors necessary for a smooth deployment and transition to ongoing operations. It encompasses the processes of preparing, installing, training, stabilising and transferring the solution to operations. This includes details about installation scenarios (i.e. at remote or branch offices), monitoring for stability and verifying the soundness of the new solution(s). Justification: This plan is the how-to guide to implement the solution into production. This plan provides detailed deployment guidelines and will help drive the solution’s deployment phase. Deployment is the beginning of the realization of business value for a given solution. A detailed a