Before I start blogging on this page, I would like to link up my earlier scribbles I made elsewhere. If you want to have a glimpse of that please click on BLOG: Arijit Chakraborti
As in my previous BLOGs, I will primarily post technology scribbles, but you may find some not-so-techie jots as well. Intermittently, I will also try to re-post some of my earlier BLOGs here.
Tuesday, September 27, 2005
IIS 6.0 Web Service Extensions
This is a new thing that I learned today. To give you a background, we have a running suite of applications on Windows2000 and IIS 5.0. Now, there is a move to upgrade the apps to Win03. After installing IIS, we realized the ASP files are not at all running on the web server while the HTML files are fine. Using the good old experience we thought it must be an installation problem, and the IIS got a faulty setup.
Then we realized the new administrative control came with IIS 6.0. It allows you to enable/disable dynamic content. Referring back to my original problem, the extension ASP was set disabled through this control, perhaps it was a default setting, or may be something really goofed up during the installation steps. But for sure, this was not a old-day's installation glitch, which could be resolved only by uninstallation and reinstallation.
IIS Manager for IIS 6.0 provides interfaces for allowing or prohibiting certain extensions related to dynamic content. You are allowed to allow/prohibit all ISAPI and CGI extensions on a server, but it's not a recommended practice to allow all ISAPI/CGI extensions to prevent the machine being suceptible to computer viruses or worms that use these technologies. So, as a good practice, allow only the required extensions.
You will find more information in the following URL http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a9fc0395-f03b-4213-9c62-1592bcfcf53f.mspx
Then we realized the new administrative control came with IIS 6.0. It allows you to enable/disable dynamic content. Referring back to my original problem, the extension ASP was set disabled through this control, perhaps it was a default setting, or may be something really goofed up during the installation steps. But for sure, this was not a old-day's installation glitch, which could be resolved only by uninstallation and reinstallation.
IIS Manager for IIS 6.0 provides interfaces for allowing or prohibiting certain extensions related to dynamic content. You are allowed to allow/prohibit all ISAPI and CGI extensions on a server, but it's not a recommended practice to allow all ISAPI/CGI extensions to prevent the machine being suceptible to computer viruses or worms that use these technologies. So, as a good practice, allow only the required extensions.
You will find more information in the following URL http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a9fc0395-f03b-4213-9c62-1592bcfcf53f.mspx
Wednesday, April 06, 2005
SendOneWay is the answer
The answer to the aynchronous web service calls found in the following URL: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwse/html/wsemessaging.asp
WSE2.0 has the implementation called SendOneWay that can be used for such purpose. Would like to go thru' more details about it.
WSE2.0 has the implementation called SendOneWay that can be used for such purpose. Would like to go thru' more details about it.
Saturday, January 22, 2005
Asynchronous Event Subscription
Getting into an interesting problem domain, where I think asynchronous event subscription could work as an answer given the architecture is based on SOA. Of course, there could be many possible ways and some would be better than this one.
The problem description can go like this:
-- Application creates/updates/deletes a specific entity. There are many units of such entity in the application.
-- Each entity is identified with a unique identifier and some specific attributes.
-- There are more than one subsidiary applications that would like to subscribe the changes happened on the units of this entity.
-- Not all subsidiary application are interested in all units undergone changes. Rather most of them would like subscribe a subset based on the specific attribute settings.
One possible solution could work like this:
-- Each unit change will publish an event
-- The event will be subsribed by the applications asynchronously.
-- All events will be subscribed by the subsidiary applications.
-- Individual applications will only do followup work if their specific attribute criteria get satisfied, i.e. if the application is interested in that particular activity.
Will do a few more work to find out what's inside.
The problem description can go like this:
-- Application creates/updates/deletes a specific entity. There are many units of such entity in the application.
-- Each entity is identified with a unique identifier and some specific attributes.
-- There are more than one subsidiary applications that would like to subscribe the changes happened on the units of this entity.
-- Not all subsidiary application are interested in all units undergone changes. Rather most of them would like subscribe a subset based on the specific attribute settings.
One possible solution could work like this:
-- Each unit change will publish an event
-- The event will be subsribed by the applications asynchronously.
-- All events will be subscribed by the subsidiary applications.
-- Individual applications will only do followup work if their specific attribute criteria get satisfied, i.e. if the application is interested in that particular activity.
Will do a few more work to find out what's inside.
Friday, August 27, 2004
Just SetAbort didn't work
I was stumped when I tried to setup a classical transaction rollback example. All I did was creating an account A class and tried to manipulate the static variable Balance. SetAbort did not work, I mean, it did not bring back the balance to its initial value.
Do I need to take care something in the resource management front?
Do I need to take care something in the resource management front?
Subscribe to:
Posts (Atom)