RockMelt, the Social Savvy Browser

RockMelt, a new browser that lives in the cloud and uses Facebook authentication to synchronize a user’s browsing experience across machines, went into limited public beta today.

It was built around the premise that the browser is busted. The thought is that older browsers aren’t made for the way we now use the web, and maybe it’s a solid way of thinking. After all, browsing is a passive activity, and the Internet is increasingly about interaction.

There are some unique concepts here, namely the fact that RockMelt lives in the cloud. This allows your “browser experience” to be, in a way, profiled. Your settings, bookmarks, etc., are all backed up online.

Using Facebook for authentication, your user environment can be replicated anywhere RockMelt is installed. And really, that’s what RockMelt is all about: The user environment.

Users of Google Chrome will feel at home, because RockMelt is built on Chromium, the open source project behind Google’s browser. The major differences are columns running down each side of the browser.

The left side depicts your favorite Facebook contacts. When a contact is listed on the left bar, you’ll be able to quickly initiate Facebook chats with them or post content to their Facebook walls. You can also easily send them e-mails through the seamless contact pop out.

Straddling the right side is your bookmarks — and here’s another area where RockMelt’s cloud is put to clever use. Bookmarks are updated from the cloud, so content is cached and waiting for you when you log on.

All in all, RockMelt is an interesting twist on the browsing experience. The social elements of the browser make for a compelling and streamlined online interaction process. And because it’s powered by Chromium, it not only supports Chromeextensions, it’s guaranteed to support the latest and greatest aspects of the web, like HTML5 and CSS3.

How Application Pools Works ? (IIS 6.0)

What are Application pools? How it actually Works? The concept of Application Pools has from IIS 6.0. Application pools are used to separate sets of IIS worker processes that share the same configuration and application boundaries. Application pools used to isolate our web application for better security, reliability, and availability and performance and keep running with out impacting each other . The worker process serves as the process boundary that separates each application pool so that when one worker process or application is having an issue or recycles, other applications or worker processes are not affected. One Application Pool can have multiple worker process.

When you run IIS 6.0 in worker process isolation mode, you can separate different Web applications and Web sites into groups known as Application pools. An Application pool is a group of one or more URLs that are served by a worker process or set of worker processes. Any Web directory or virtual directory can be assigned to an application pool. Each application pool is given its own set of server resources. That way, if a Web site crashes, it won’t effect sites in other application pools.

A classic example of this is a Web site with a memory leak. If all of the Web sites hosted on a particular server were to share system resources, and one of the Web sites had a memory leak, it could potentially take memory away from the other hosted sites. If the leaky site were in its own application pool though, the memory leak would not effect any other site because each application pool has its own server resources (including memory).

Main idea behind application pools are
1. Isolation of Different Web Application
2. Individual worker process for different web application
3. More reliably web application
4. Better Performance

For more information check this URL from MSDN.

Hope this is useful

Under standing Local Service, Local System and Network Service?

The main difference between these Local Service, Local System and Network Service mainly relay on the security principals. I have website I need to configure remote connections. When we use SQL Server, so when allowing remote connections and you might think which Service account you should use to run SQL Server.

You should use Local non-system or Service account. If this SQL Server service require to access the network resources you can use a ordinary Domain account.

• Domain User Account
  If the service must interact with network services, access domain resources like file shares or if it uses linked server connections to other computers running SQL Server, you might use a minimally-privileged domain account. Many server-to-server activities can be performed only with a domain user account. This account should be pre-created by domain administration in your environment.
• Local User Account
  If the computer is not part of a domain, a local user account without Windows administrator permissions is recommended.

Following are NOT advised as it grant more privileges than required for running SQL Server Services

• Local System is a very high-privileged built-in account. It has extensive privileges on the local system and acts as the computer on the network. The actual name of the account is "NT AUTHORITY\SYSTEM".
• The Local Service account is a built-in account that has the same level of access to resources and objects as members of the Users group. This limited access helps safeguard the system if individual services or processes are compromised. Services that run as the Local Service account access network resources as a null session without credentials. Be aware that the Local Service account is not supported for the SQL Server or SQL Server Agent services. The actual name of the account is "NT AUTHORITY\LOCAL SERVICE".
• The Network Service account is a built-in account that has more access to resources and objects than members of the Users group. Services that run as the Network Service account access network resources by using the credentials of the computer account. The actual name of the account is "NT AUTHORITY\NETWORK SERVICE"

Please consider the below recommendations:

• Always run SQL Server services by using the lowest possible user rights.
• Use a specific low-privilege user account or domain account instead of a shared account for SQL Server services.
• Use separate accounts for different SQL Server services.
• Do not grant additional permissions to the SQL Server service account or the service groups

Date Formatting in C#

Date formatting in C# using string object

Specifier	Description	Output
d	Short Date	20/10/1983
D	Long Date	20 October 1983
t	Short Time	21:20
T	Long Time	21:20:59
f	Full date and time	20 October 1983 21:20
F	Full date and time (long)	20 October 1983 21:20:59
g	Default date and time	20/10/1983 21:20
G	Default date and time (long)	20/10/1983 21:20:59
M	Day / Month	20 October
r	RFC1123 date	Thu, 20 Apr 1983 21:20:59 GMT
s	Sortable date/time	1983-10-20T21:20:59
u	Universal time, local timezone	1983-10-20 21:20:59Z
Y	Month / Year	October 1983
dd	Day	20
ddd	Short Day Name	Thu
dddd	Full Day Name	Thursday
hh	2 digit hour	09
HH	2 digit hour (24 hour)	21
mm	2 digit minute	20
MM	Month	10
MMM	Short Month name	Apr
MMMM	Month name	October
ss	seconds	59
tt	AM/PM	PM
yy	2 digit year	07
yyyy	4 digit year	1983
:	seperator, e.g. {0:hh:mm:ss}	09:20:59
/	seperator, e.g. {0:dd/MM/yyyy}	20/10/1983

Example using the specifier with data object

DateTime now = DateTime.Now;
Console.WriteLine(now.ToString("d"));

Download: SQL Server Sample Databases

SQL Server 2008R2 product sample databases are now available.
SQL Azure sample databases are now available.
SQL Server 2008 product sample databases are still available. If you are having difficulties with the current installer, please refer this Database Installer Help.
SQL Server 2005 product sample databases are still available.

For more help most sample databases and sample database business scenarios are documented on MSDN.