Skip to main content

Posts

Showing posts from December, 2009

Storage and use of explosives

Do’s

1. Store explosives only in licensed magazine.
2. Always maintain magazine in good condition.
3. Always keep gangway of 60 cm between stack of explosives boxes and wall.
4. Get all lightening conductors on magazine tested for continuity and resistance once in a year. The resistance of lightening conductors should less than 10 ?.
5. Mark license no. And validity prominently on licensed premises.
6. Mark 12 mm thick red line 2.5 m above floor level inside the magazine and do not stack explosives boxes above it.
7. Provide fencing at a distance of 15 m from magazine and keep the fenced area free of vegetation.
8. Always keep stock of explosives within licensed capacity.
9. Always issue old explosives first.
10. Provide security guards round the clock.
11. Keep security guard’s shelter at a distance of 30 m from magazine.
12. Always sell explosives to pe…

Dos & Don'ts - Fireworks Display

Dos & Don'ts - Fireworks Display

* Buy fireworks of authorized/reputed manufacturers only.
* Light only one firework at a time, by one person. Others should watch from a safe distance.
* Keep the fireworks to be used at a safer place.
* Organize a community display of fireworks rather than individuals handling crackers.
* Always use a long candle/'phooljhari' for igniting fire crackers and keep elbow joint straight to increase the distance between the body and the crackers.
* Keep two buckets of water handy. In the event of fire, extinguish flame by pouring water from the buckets. Every major fire is small when it starts.
* In case of burns, pour large quantity of water on the burnt area.
* In case of major burns, after extinguishing the fire, remove all smoldering clothes. Wrap the victim in a clean bedsheet.
* The patient should be taken to a burns specialist or a major hospital. Don't panicky.
* In case of eye burns, wash the eye wi…

Maintenance Tips for Your PC

Operating & Environment Conditions

* Do not place a PC directly near a heating or cooling source, such as heating vents or air conditioners. Both excessive heat and cold can damage a PC. This includes putting the PC in the path of direct sunlight.
* Manufacturers often recommend that PCs be in a humidity-controlled environment, but again the PC should not be positioned so that an air conditioner is blowing cool air directly onto the unit (as temperature drops, the likelihood of static electricity increases).
* Keep the PC's air vents and fans unobstructed and free of dust.
* Do not smoke around a PC. Cigarette smoke can damage exposed metal contacts.
* Do not place a PC near water sources that can splash onto the components or drip down into them. This includes open windows through which rain can come and also under plants than can drip water down into them.
* Do not connect power sources directly into wall outlets but rather connect them first to some form …

List

list of Web service protocols.

BEEP - Blocks Extensible Exchange Protocol
E-Business XML
Hessian
JSON-RPC
Qworum - Defines the concept of Qworum services, which are building blocks for web applications. Qworum services return XML results like conventional RPC services. In addition they can interact with the end-user through web pages during the call, and they can call other Qworum services.
REST (Representational State Transfer)
SOAP - outgrowth of XML-RPC, originally an acronym for Simple Object Access Protocol
Universal Description, Discovery, and Integration (UDDI)
Web Services Description Language (WSDL)
WSFL - Web Services Flow Language (superseded by BPEL)
WSCL - Web Services Conversation Language
XINS Standard Calling Convention - HTTP parameters in (GET/POST/HEAD), POX out
XLANG - XLANG-Specification (superseded by BPEL)
XML-RPC - XML Remote Procedure Call

List of markup languages for web services.

Web template
Web Services Description Language (WSDL) from the W3C
XML Interface for Network Serv…

.NET Framework

The .NET Framework is designed to fulfill the following objectives:

* To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
* To provide a code-execution environment that minimizes software deployment and versioning conflicts.
* To provide a code-execution environment that promotes safe execution of code, including code created by an unknown or semi-trusted third party.
* To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
* To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
* To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

Give donations to Bharath Foundation

Project Estimations

1. Project estimates must be based on the application’s architecture. Making estimates based on an application’s architecture should give you a clear idea of the length of the entire development project phase. Moreover, an architecture-based estimation provides you a macro-level view of the resources needed to complete the project.
2. Project estimations should also come from the ground up. All estimates must add up, and estimating the collective efforts of the production teams that work on the application’s modules helps identify the number of in-house and outsourced consultants that you need to hire for the entire project, as well as have a clear idea of the collective man-hours required to code modules or finish all features of the application. Ground-up estimates are provided by project team members and do not necessarily match top-level estimates exactly. In this case, it is best to add a percentage of architecture-based estimates to give room to possible reworks, risks, and o…