.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Interview Question >> Sql Server >> Post New Question Subscribe to Interview Questions

Explain architecture of Notification Services?

Posted By :John     Posted Date :April 06, 2009    Points :10   Category :Sql Server 
Notification Services applications are based on a subscriber/subscription model.
The Key components in a Notification Services application are

Subscriber: A user or application that requests and receives the notification
Subscription: A request for information, delivery mechanism, and destination for requested notifications. For example change of a stock price.
Event: A piece of information, in which the subscriber is interested. For example as soon as a stock price has changed an event can be generated that's processed within SQLNS.
Notification: A message containing the information requested by the subscriber in the subscription.

SQLNS executes the following steps whenever it generates a new notification and sends it to registered subscribers:

.Subscribers create subscriptions with a subscription management application, such as an ASP.NET or Windows Forms front end.
.Subscription management is the only part of an SQLNS application where users or applications are actively involved in the process. You generate subscriptions using a managed assembly shipped with SQLNS.
.The Notification Application collects events, which are processed within the SQLNS application.
.SQLNS uses T-SQL statements to assign events to the subscriptions registered in the first step.
.SQLNS generates new notifications whenever it finds an assignment.
.A Formatter formats the new notification, and SQLNS delivers it through a delivery channel to the registered target device of the subscriber.

You can also find related Interview Question to Explain architecture of Notification Services?  below: 

What are notification services?

  
Notification Services is a programming framework based on XML and T-SQL. It is used to create applications that generate and send messages to subscribers.

Notifications can be sent according to a schedule, or in response to conditions or events. Notifications can be sent to a wide variety of devices. For example, a notification can be sent to a user's cellular phone, personal digital assistant (PDA), Microsoft Windows Messenger, or e-mail account. Because these devices often accompany the user, notifications are ideal for sending high-priority information.

We can create the notification Services in 2 ways:
The first would be to build everything from scratch, second is to use the SQL Server 2005 Notification Services (SQLNS), which is a new API, intended to help you build notification applications. SQLNS applications are always hosted inside the SQL Server or inside a Windows Service. (More...)

What are basic components of Notification services?

  
Notification Services applications are based on a subscriber/subscription model.
The Key components in a Notification Services application are

Subscriber
A user or application that requests and receives the notification

Subscription
A request for information, delivery mechanism, and destination for requested notifications. For example change of a stock price.

Event
A piece of information, in which the subscriber is interested. For example as soon as a stock price has changed an event can be generated that's processed within SQLNS.

Notification
A message containing the information requested by the subscriber in the subscription (More...)

Which are the two XML files needed for notification services?

  
SQLNS Configuration Files need a pair of XML-based configuration files: the Instance Configuration file and the Application Definition file.

Instance Configuration file
To host a SQLNS application you need an instance of SQLNS. This instance also stores subscriber information, which can be shared among all SQLNS applications hosted on an instance.

Application Definition File
This file to configure the whole SQLNS application structure along with all necessary metadata. (More...)

Explain the three services model (three-tier application).

  
Presentation (UI), business (logic and underlying code) and data (from storage or other sources). (More...)

Explain the three services model commonly know as a three-tier application.

  
Presentation (UI), Business (logic and underlying code) and Data (from storage or other sources). (More...)

What is the relationship between the .NET Framework and COM+ Services?

  
The .NET Framework gives you full access to COM+ services, while also making it easier to build serviced components.
.NET Framework components can be added to a COM+ application. There they can take advantage of automatic component services such as transactions, object pooling, queued components, events, and so on. (More...)

What is the relationship between the .NET Framework and COM+ Services?

  
The .NET Framework gives you full access to COM+ services, while also making it easier to build serviced components.
.NET Framework components can be added to a COM+ application. There they can take advantage of automatic component services such as transactions, object pooling, queued components, events, and so on. (More...)

Explain the concept of Reentrancy?

  
It is a useful, memory-saving technique for multiprogrammed timesharing systems. A Reentrant Procedure is one in which multiple users can share a single copy of a program during the same period. Reentrancy has 2 key aspects: The program code cannot modify itself, and the local data for each user process must be stored separately. Thus, the permanent part is the code, and the temporary part is the pointer back to the calling program and local variables used by that program. Each execution instance is called activation. It executes the code in the permanent part, but has its own copy of local variables/parameters. The temporary part associated with each activation is the activation record. Generally, the activation record is kept on the stack.

Note: A reentrant procedure can be interrupted and called by an interrupting program, and still execute correctly on returning to the procedure. (More...)

Explain Belady's Anomaly?

  
Also called FIFO anomaly. Usually, on increasing the number of frames allocated to a process' virtual memory, the process execution is faster, because fewer page faults occur. Sometimes, the reverse happens, i.e., the execution time increases even when more frames are allocated to the process. This is Belady's Anomaly. This is true for certain page reference patterns. (More...)

NET Remoting Versus Web Services?

  
With the advent of .NET and the .NET Framework, Microsoft introduced a set of new technologies in the form of Web services and .NET remoting. .NET remoting and ASP.NET Web services are powerful technologies that provide a suitable framework for developing distributed applications. It is important to understand how both technologies work and then choose the one that is right for your application.

The Web services technology enables cross-platform integration by using HTTP, XML and SOAP for communication thereby enabling true business-to-business application integrations across firewalls. Because Web services rely on industry standards to expose application functionality on the Internet, they are independent of programming language, platform and device.

Remoting is .a technology that allows programs and software components to interact across application domains, processes, and machine boundaries. This enables your applications to take advantage of remote resources in a networked environment.

Both Web services and remoting support developing distributed applications and application integration, but you need to consider how they differ before choosing one implementation over the other. In this article, I will show the differences between these two technologies. I will present samples for each type of implementation and identify when to use which technology. (More...)

Explain manifest & metadata.

  
Manifest is metadata about assemblies. Metadata is machine-readable information about a resource, or ""data about data." In .NET, metadata includes type definitions, version information, external assembly references, and other standardized information. (More...)

Explain the life cycle of an ASP .NET page.

  
Life cycle of ASP.Net Web Form
Page Request >> Start >> Page Init >> Page Load >> Validation >>
PostBack Event Handling >> Page Rendering >> Page Unload
Page Request - When the page is requested ASP.Net determines
whether the page is to be parsed and compiled or a cached verion
of the page is to be sent without running the page.
Start - Page propertied REQUEST and RESPONSE are SET, if the
page is pastback request then the IsPostBack property is SET and
in addition to this UICulture property is also SET.
Page Initilization - In this the UniqueID of each property is SET.
If the request was postback the data is not yet loaded from the
viewstate.
Page Load - If it was a postback request then the data gets loaded
in the control from the ViewState and control property are set.
Validation - If any control validation present, they are performed
and IsValid property is SET for each control.
PostBack Event Handling - If it was a postback request then any
event handlers are called.
Page Rendering - Before this the viewstate is saved from the page
and RENDER method of each page is called.
Page Unload - Page is fully rendered and sent to the client(Browser)
and is discarded. Page property RESPONSE and REQUEST are unloaded. (More...)

Explain manifest & metadata?

  
Manifest is metadata about assemblies. Metadata is machine-readable information about a resource, or ""data about data." In .NET, metadata includes type definitions, version information, external assembly references, and other standardized information.

Manifest: Manifest describes assembly itself. Assembly Name, version number, culture, strong name, list of all files, Type references, and referenced assemblies.

Metadata: Metadata describes contents in an assembly classes, interfaces, enums, structs, etc., and their containing namespaces, the name of each type, its visibility/scope, its base class, the nterfaces it implemented, its methods and their scope, and each method's parameters, type's properties, and so on.

Shashi Ray (More...)

Explain Virtual Function in C#.

  
Virtual functions implement the concept of polymorphism are the same as in C#, except that you use the override keyword with the virtual function implementaion in the child class.

The parent class uses the same virtual keyword. Every class that overrides the virtual method will use the override keyword.


class Shape{
public virtual void Draw()
{ Console.WriteLine("Shape.Draw") ; }
}
class Rectangle : Shape{
public override void Draw()
{ Console.WriteLine("Rectangle.Draw"); }
} (More...)

Quick Links For Interview Questions Categories:
ASP.Net Windows Application   .NET Framework   C#   VB.Net   ADO.Net  
Sql Server   SharePoint   Silverlight   OOPs   JQuery   JavaScript/VBScript
Biztalk Patten/Practices .IIS WCF WPF WWF
Networking Aptitude Others   All      

Find questions, FAQ's and their answers related to .NET, C#, Vb.Net, Sql Server and many more.

 
Now you can find lots of .NET, C#, Vb.Net, SQL Server,Windows, ASP.Net related Questions and their Answers here at www.dotnetspark.com. Our aim is to help you pass your certification Exams (MCP, MCSD, MCAD etc.,) with flying scores and get good name in your company.

So, Start looking our Interview Question section daily and improve your .NET Skills. You can also help others by posting Interview Questions and their Answers in this section.


Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend