Internet Marketing, Website Designing Ethics & Development blog
Everything About Websites and Online Marketing

There are hundreds and thousands of fonts that are used in web design. Different kinds of fonts are used in different kinds of websites, for different purposes based on the type of content the website has. There are so many kinds of styles that you may be spoilt for choice and thus it is good for you to first understand the basics and details of the fonts that are used for web design purposes.

The different website fonts

There are so many kinds of fonts that are used for web design. Some of the most popular and common ones are:

• Sans Serif – Sans Serif is one of the most common and simple font styles used for web design. Sans means without and Serif means tail on the letters. Thus the style Sans Serif will have to involve the design of the letters which are without any tails.
• Slab serif – Slab Serif is the font style where there are those tails with the letter style and these tails are more in the form of slabs. In case of the simple serf in general, the serifs are given in a slanting way. But in case of the Slab Serif thing, the tails lack the slant and are more like slabs.
• Oldstyle – In Oldstyle, the style is more of the old kind where flags are used in the lowercase letters. For example, the lower case ‘l’ is going to have a flag at the bottom.
• Script – This font gives the visuals of the handwritten letters. This type again has varieties within them.
• Arial – In Arial there are no serifs and thus is just another type of the Sans Serif style.
• Verdana – Verdana is mainly to help the small sized screen letters readable. This too is a Sans Serif type and are thus without any tails.

There are various other kinds of fonts that can help you in designing the websites in various other ways. Some of the other styles are the Times New Roman, Georgia, Trebuchet, and Century Gothic and so on.

The Global.asax file, also known as the ASP.NET application file, is an optional file that contains code for responding to application-level events raised by ASP.NET or by HttpModules. The Global.asax file resides in the root directory of an ASP.NET-based application. At run time, Global.asax is parsed and compiled into a dynamically generated .NET Framework class derived from the HttpApplication base class with a custom property named NumberOfRequests. This property retrieves the number of request made for the page at the current path..

Events Of Global.asax

The Global.asax file contains the following events:

• Application_Init: It is fired when an application initializes or is first called. It’s invoked for all HttpApplication object instances.
• Application_Disposed: It is fired just before an application is destroyed. This is the ideal location for cleaning up previously used resources.
• Application_Error: It is fired when an unhandled exception is encountered within the application.
• Application_Start: It is fired when the first instance of the HttpApplication class is created. It allows you to create objects that are accessible by all HttpApplication instances.
• Application_End: It is fired when the last instance of an HttpApplication class is destroyed. It’s fired only once during an application’s lifetime.
• Application_BeginRequest: It is fired when an application request is received. It’s the first event fired for a request, which is often a page request (URL) that a user enters.
• Application_EndRequest: The last event fired for an application request.
• Application_PreRequestHandlerExecute: It is fired before the ASP.NET page framework begins executing an event handler like a page or Webservice.
• Application_PostRequestHandlerExecute: It is fired when the ASP.NET page framework is finished executing an event handler.
• Applcation_PreSendRequestHeaders: It is fired before the ASP.NET page framework sends HTTP headers to a requesting client (browser).
• Application_PreSendContent: It is fired before the ASP.NET page framework sends content to a requesting client (browser).
• Application_AcquireRequestState: It is fired when the ASP.NET page framework gets the current state (Session state) related to the current request.
• Application_ReleaseRequestState: It is fired when the ASP.NET page framework completes execution of all event handlers. This results in all state modules to save their current state data.
• Application_ResolveRequestCache: It is fired when the ASP.NET page framework completes an authorization request. It allows caching modules to serve the request from the cache, thus bypassing handler execution.
• Application_UpdateRequestCache: It is fired when the ASP.NET page framework completes handler execution to allow caching modules to store responses to be used to handle subsequent requests.
• Application_AuthenticateRequest: It is fired when the security module has established the current user’s identity as valid. At this point, the user’s credentials have been validated.
• Application_AuthorizeRequest: It is fired when the security module has verified that a user can access resources.
• Session_Start: It is fired when a new user visits the application Website.
• Session_End: It is fired when a user’s session times out, ends, or they leave the application Web site.

The Application_Init and Application_Start events are fired once when the application is first started. Likewise, the Application_Disposed and Application_End are only fired once when the application terminates. In addition, the session-based events (Session_Start and Session_End) are only used when users enter and leave the site. The remaining events deal with application requests, and they’re triggered in the following order:

• Application_BeginRequest
• Application_AuthenticateRequest
• Application_AuthorizeRequest
• Application_ResolveRequestCache
• Application_AcquireRequestState
• Application_PreRequestHandlerExecute
• Application_PreSendRequestHeaders
• Application_PreSendRequestContent
• <<code is executed>>
• Application_PostRequestHandlerExecute
• Application_ReleaseRequestState
• Application_UpdateRequestCache
• Application_EndRequest

An Interface is a named collection of semantically similar abstract members or functions. A class or a structure may follow a behaviour that is prescribed by an interface. The keyword interface is used to create an interface. Note that while defining members inside an interface, there is no need to specify the access specifier, as they are public by default.

See syntax below:

public interface IBooks

{

long int ISDN_No;

}

As a convention, interfaces in .NET are prefixed with an “I” in uppercase, as a good programming practice.

Methods inside an interface do not have a body. They only signify that such a method should exist in the implementing class or structure.

Classes that display a common set of features, such as having similar types of member variables or member functions, are designed in such a way that they implement a common interface.

How to implement an interface in C#?

An interface may be implemented using the keyword “implements” in VB.NET, and using a colon in C#. See code C# example below:

//In C#

interface IBooks

{

long int Cost { get; } //Interface property

}

//ComputerBooks is a class that implements an Interface IBooks

public class ComputerBooks : IBooks

{

// Implementation of the property

public long int Cost

{

get { return 100; } //Read only value

}

}

A quick recall about “Reported Attack Site”.
Report attack site is a red color warning page which is shown by the browser instead of showing the actual site. It is a warning that visitor see on his computer screen in the browser
that this particular website could contain -

1) Malware Attacks
2) Antivirus
3) The hosting may have phishing page
4) The source computer where the data is being upload infected by trojan, malware of other viruses.
5) Insecure folder permissions will be there.
Website is warning for the people and its negative effects
1) People recognized your site as blacklisted or spam or dangerous
2) People will be afraid visiting yoru website and you’ll recieve 0 traffic.
3) Google shows warning and people trust google, that means no one dares to get in touch with you.

report site attack warning and suggestion image

Removal of  ”Report attack site warning” ?
1) Having badware means the security of your website is being compromised, it may be your system, hosting, database used. First, check out the source. Scan everything and contact your hosting provider as well, as this may be some issue from his end too.

2) Sample of the dangerous URL’s should be viewed in the webmaster tools.

3) Necessary changes should be made according to :stopBadware.org’s security tips, go through this.

4) New: Malware review request should be made to the google via. google webmaster tools.

Malware effected site reconsideration by google

5) Check the status of the website review or reconsideration.

* If google feels that the site is still harmful, it’ll provide you with the list of dangerous URL’s.
* If the site is being determined as clean, you can expect the demolition of malware warning within the next 24 hours.

6) If you feel that your ranking has been effected then you can also fill the reconsideration form, here is the link for mored – http://goo.gl/577wp

In such cases and warning, most probably you need to send a reconsideration request to google that you are playing it all fair. If you are honest in the game, you will not suffer.

As our current generation consists of internet, computers, laptops, websites and social media networks. A lot of people give preference to online presence, to promote their business and services. Creating a great website, which showcases the area of expertise of a particular company all across the web has become a necessity for every organization, no matter small or large. After the completion of the web site, it is uploaded to the server (or make available on the internet) and it becomes live. Now, the site is online, you are happy to see the work of the designers and the development team. Your site is looking good and it’s a healing experience. But wait a minute! There something entirely different behind the curtain.

One morning you are happy, weather is good, birds in the sky are flying high. You go to your office turn your computer system on. First of all, you think why not check out your very own cute site. You type in the domain name in the browser and ….… hey what is this “Report Attack Site”. The red color background having a warning from the king of search engines google. This ugly page opens instead of your index page. Where does it come from? How your site turned into a site unavailable for the users? You haven’t made it for false practices, then why it is flagged by search engines and Firefox prevents your site being opened. Like generally, if some kind of virus is there you will open the web page of the site, you will see a warning which is mostly sent from Google team exactly looks like the image below:

Warning declares that there is a virus which can damage other people software’s also and your site is a thread to their systems. So, to avoid that kind of risks this message is shown.  Usually this type of error will be shown In Firefox browser (3. 0r 3+). What you have to do is – CLEAN THIS VIRUS. But how could we do it? Due to this warning, visitors don’t open the webpage and again afraid of their system being infected. In this whole process all your hopes will turn into despair. The reputation your site was enjoying would be demolished. All the efforts of yours, in terms of making a successful online presence would go in vain.

First question, that comes in mind, what the hell this attack is and how to escape from this online disease?

Actually, this is a malware attack, malicious software, which is specially designed to damage the computer systems, without the owner’s informed consent (obviously). After your site is being flagged by Google, you will be notified by an email. Numerous articles have already been written on the issue. Millions of threads are available in forums. Different peoples have varied opinions. Some are successful and the others thoroughly confuse you. So is there any proper guide that tells exactly where the problem lies and what is the root cause.  Are there any solutions, preventions and a stepwise guide, keep your website safe enough to prevent such attacks?

Sure, there are simple steps to get rid of this hazard. I shall discuss in detail in the next post, how to get rid of this problem. I know there are many people who don’t have any idea how to deal with it.

See you soon.