Maven Dependency vs dependency management

dependencies

<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
</dependency>
</dependencies>

Dependency management

<dependencyManagement>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8</version>
</dependency>
</dependencies>
</dependencyManagement>

Dependency Management allows to consolidate and centralize the management of dependency versions without adding dependencies which are inherited by all children.

This is especially useful when you have a set of projects (i.e. more than one) that inherits a common parent.

In the parent POM, the main difference between the <dependencies> and <dependencyManagement> is this:

  • Artifacts specified in the <dependencies> section will ALWAYS be included as a dependency of the child module(s).
  • Artifacts specified in the <dependencyManagement> section, will only be included in the child module if they were also specified in the <dependencies> section of the child module itself.

    Why is it good?

  • because you specify the version and/or scope in the parent, and you can leave them out when specifying the dependencies in the child POM. This can help you use unified versions for dependencies for child modules, without specifying the version in each child module
  • <dependencyManagement> allows to easily upgrade/downgrade dependencies based on need, in other scenario this needs to be exercised at every child pom level

    Ref: https://stackoverflow.com/q/2619598

Posted in technology, Techonlogy, Uncategorized, web | Tagged , , | Leave a comment

தன்ராம் சிங்

நாஞ்சில்நாடன்

 நாஞ்சில் நாடன்
சிங் எனும் துணைப்பெயர்  கொண்டவரெல்லாம்  பஞ்சாபி என எண்ணிக்கொள்ள வேண்டாம். தன்ராம் சிங் பஞ்சாபி அல்ல. கேட்டால் அவன் தன்னை நேப்பாளி என்பான். அவர்களுக்கும் சிங் என்று துணைப்பெயர் உண்டு. ஆனால் உண்மையில் தன்ராம் சிங் திபேத்துக்காரன். நேப்பாளி என்று சொன்னால் வடநாட்டில் சமூக அங்கீகாரம் சற்று அதிகம் என்பதை உங்களுக்குத் தெரியச் சொல்கிறேன். நேப்பாளிகளுக்கு சற்று மேலான தோற்றப் பொலிவு உண்டு. தன்மையில் கூரான மறம் உண்டு. திபெத்துக்கரர்களுக்கும் வெள்ளை நிறம்தான், கண்கள் இடுக்கமானவைதான், முகத்திலும் உடலிலும் நிரப்பாக மயிர் வளர்வதில்லைதான். எனினும் நேப்பாளிகள் வேறு, திபேத்தியர்கள் வேறு.
கூர்க்கா வேலை செய்யும் யாரைக் கேட்டாலும் நேப்பாளி என்பார்கள். நேப்பாளிகளுக்கு அதில் சற்று மன வருத்தம்தான்.  ‘காஞ்சா’ என்று மாருதி கார் விளம்பரத்தில் வரும் சொல்லைக்கூட அவர்கள் ஏற்றுக்கொள்வதில்லை. தன்ராம் சிங்கை துளைத்துக் கேட்டால், ‘திபேக்’ என்பான். அவனுக்கு ‘திபேத்’ என்று சொல்ல வராது. ஒரு வேலை அவனது பிராந்திய மொழிக் கொச்சையில் ‘திபேக்’ என்றால் ‘திபேத்’ தோ என்னவோ!
எனக்கு பம்பாயில்தான் கூர்க்காக்கள் முதலில் அறிமுகம். நாற்பது பேர் வேலை செய்த தொழிற்சாலையில் முதலில் மகேந்திர சிங் என்றொரு கூர்க்கா இருந்தான். அவன் அசல் நேப்பாளி. தொழிலாளர்கள் யாரும் அவனைச் சீண்ட முடியாது. தலையில் ஜெனரல் மானேக்ஷா  பாணித் தொப்பியும் காலில் சாக்சும் பூட்சும் காக்கி கால்சட்டையும் முழுக்கைச் சட்டையும் இடையில் பெல்ட்டும் செருகிய சற்றே…

View original post 1,439 more words

Posted in Uncategorized | Leave a comment

GraphQL – The Future of Microservices?

via GraphQL – The Future of Microservices?

Posted in Uncategorized | Leave a comment

ஈரேழு பதினாலு லோகம் அர்த்தம்

ஈரேழு பதினாலு லோகம்
((இரு+ஏழு=பதினாலு+லோகம்))

இந்துமத வேத மரபின்படி இந்தப் பிரபஞ்சத்தில் பதினான்கு உலகங்கள் இருப்பதாக நம்பப்படுகிறது…ஈரேழு என்றால் இரண்டு ஏழு அதாவது பதினான்கு என்று அர்த்தம்…மேலுலகங்கள் ஏழு மற்றும் கீழுலகங்கள் ஏழு மொத்தம் பதினான்கு உலகங்கள் எனக் கணக்கு…நாம் வாழும் பூவுலகம் மேலுலகத்தில் உள்ளதாகும்…ஆகவே பூவுலகிற்கு மேல் ஆறு உலகங்களும், கீழே ஏழு உலகங்களும் இருக்கின்றன. அவைகள்;-

7. சத்யலோகம்
6. தபோலோகம்
5. ஜனோலோகம்
4. மஹர்லோகம்
3. சுவர்லோகம்
2. புவர்லோகம்

↑ மேல் உலகங்கள் ஏழு
______________________________________
1. பூலோகம் – நாம் வாழும் மண்ணுலகு
_____________________________________

↓கீழ் உலகங்கள் ஏழு

அதலலோகம்
விதலலோகம்
சுதலலோகம்
தலாதலலோகம்
மகாதலலோகம்
ரஸாதலலோகம்
பாதாளலோகம்

 

Refer: http://www.siththarkal.com/2013/12/blog-post_23.html

 

Posted in history, tamil, Uncategorized | Tagged , | Leave a comment

HTTP Status Codes & Description

This Gist code contains list of http

  • HTTP Status Codes
  • Description
  • Type Of Response
  • Reference URL

in JSON Format.

{
"http_codes":[
{
"code":100,
"status":"Continue",
"type":"Information responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/100",
"description":"This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished."
},
{
"code":101,
"status":"Switching Protocol",
"type":"Information responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/101",
"description":"This code is sent in response to an Upgrade request header by the client, and indicates the protocol the server is switching too"
},
{
"code":103,
"status":"Processing ",
"type":"Information responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/103",
"description":"This code indicates that the server has received and is processing the request, but no response is available yet."
},
{
"code":200,
"status":"OK",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/200",
"description":"The request has succeeded. The meaning of a success varies depending on the HTTP method: \n GET: The resource has been fetched and is transmitted in the message body.\n HEAD: The entity headers are in the message body. \n POST: The resource describing the result of the action is transmitted in the message body.\n TRACE: The message body contains the request message as received by the server"
},
{
"code":201,
"status":"Created",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/201",
"description":"The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request."
},
{
"code":202,
"status":"Accepted",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/202",
"description":"The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing."
},
{
"code":203,
"status":"Non-Authoritative Information",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/203",
"description":"This response code means returned meta-information set is not exact set as available from the origin server, but collected from a local or a third party copy. Except this condition, 200 OK response should be preferred instead of this response"
},
{
"code":204,
"status":"No Content",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204",
"description":"There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones."
},
{
"code":205,
"status":" Reset Content",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/205",
"description":"This response code is sent after accomplishing request to tell user agent reset document view which sent this request."
},
{
"code":206,
"status":"Partial Content",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/206",
"description":"This response code is used because of range header sent by the client to separate download into multiple streams."
},
{
"code":207,
"status":"Multi-Status (WebDAV)",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/207",
"description":"A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate."
},
{
"code":208,
"status":"Multi-Status (WebDAV)",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/208",
"description":"Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly."
},
{
"code":226,
"status":"226 IM Use",
"type":"Successful responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/226",
"description":"The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance."
},
{
"code":300,
"status":"Multiple Choice",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/300",
"description":"The request has more than one possible responses. User-agent or user should choose one of them. There is no standardized way to choose one of the responses."
},
{
"code":301,
"status":"Moved Permanently",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/301",
"description":"This response code means that URI of requested resource has been changed. Probably, new URI would be given in the response."
},
{
"code":302,
"status":" Found",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/302",
"description":"This response code means that URI of requested resource has been changed temporarily. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests."
},
{
"code":303,
"status":"See Other",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/303",
"description":"Server sent this response to directing client to get requested resource to another URI with an GET request."
},
{
"code":304,
"status":"Not Modified",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304",
"description":"This is used for caching purposes. It is telling to client that response has not been modified. So, client can continue to use same cached version of response."
},
{
"code":305,
"status":"Use Proxy",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/305",
"description":"Was defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy."
},
{
"code":306,
"status":"unused",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/306",
"description":"This response code is no longer used, it is just reserved currently. It was used in a previous version of the HTTP 1.1 specification."
},
{
"code":307,
"status":"Temporary Redirect",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/307",
"description":"Server sent this response to directing client to get requested resource to another URI with same method that used prior request. This has the same semantic than the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request."
},
{
"code":308,
"status":"Permanent Redirect",
"type":"Redirection messages",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/308",
"description":"This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request."
},
{
"code":400,
"status":"Bad Request",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
"description":"This response means that server could not understand the request due to invalid syntax."
},
{
"code":401,
"status":"Unauthorized",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401",
"description":"Authentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible."
},
{
"code":402,
"status":"Payment Required",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402",
"description":"This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems however this is not used currently."
},
{
"code":403,
"status":"Forbidden",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403",
"description":"Client does not have access rights to the content so server is rejecting to give proper response."
},
{
"code":404,
"status":"Not Found",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
"description":"Server can not find requested resource. This response code probably is most famous one due to its frequency to occur in web."
},
{
"code":405,
"status":"Method Not Allowed",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405",
"description":"The request method is known by the server but has been disabled and cannot be used. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code."
},
{
"code":406,
"status":"Not Acceptable",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406",
"description":"This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content following the criteria given by the user agent."
},
{
"code":407,
"status":"Proxy Authentication Required",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/407",
"description":"This is similar to 401 but authentication is needed to be done by a proxy."
},
{
"code":408,
"status":"Request Timeout",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408",
"description":"This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message."
},
{
"code":409,
"status":"Conflict",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/409",
"description":"This response would be sent when a request conflict with current state of server."
},
{
"code":410,
"status":"Gone",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410",
"description":"This response would be sent when requested content has been deleted from server."
},
{
"code":411,
"status":"Length Required",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/411",
"description":"Server rejected the request because the Content-Length header field is not defined and the server requires it."
},
{
"code":412,
"status":"Precondition Failed",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/412",
"description":"The client has indicated preconditions in its headers which the server does not meet."
},
{
"code":413,
"status":"Payload Too Large",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/413",
"description":"Request entity is larger than limits defined by server; the server might close the connection or return an Retry-After header field."
},
{
"code":414,
"status":"URI Too Long",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/414",
"description":"The URI requested by the client is longer than the server is willing to interpret."
},
{
"code":415,
"status":"Unsupported Media Type",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415",
"description":"The media format of the requested data is not supported by the server, so the server is rejecting the request."
},
{
"code":416,
"status":"Requested Range Not Satisfiable",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/416",
"description":"The range specified by the Range header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data."
},
{
"code":417,
"status":"Expectation Failed",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/417",
"description":"This response code means the expectation indicated by the Expect request header field can't be met by the server."
},
{
"code":418,
"status":"I'm a teapot",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418",
"description":"The server refuses the attempt to brew coffee with a teapot."
},
{
"code":421,
"status":"Misdirected Request",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/421",
"description":"The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI."
},
{
"code":422,
"status":"Unprocessable Entity (WebDAV)",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/422",
"description":"The request was well-formed but was unable to be followed due to semantic errors."
},
{
"code":423,
"status":"Locked (WebDAV)",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/423",
"description":"The resource that is being accessed is locked."
},
{
"code":424,
"status":"Failed Dependency (WebDAV)",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/424",
"description":"The request failed due to failure of a previous request."
},
{
"code":426,
"status":"Upgrade Required",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/426",
"description":"The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s)."
},
{
"code":428,
"status":"Precondition Required",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/428",
"description":"The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict."
},
{
"code":429,
"status":"Too Many Requests",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429",
"description":"The user has sent too many requests in a given amount of time (rate limiting)."
},
{
"code":431,
"status":"Request Header Fields Too Large",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/431",
"description":"The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields."
},
{
"code":451,
"status":"Unavailable For Legal Reasons",
"type":"Client error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/451",
"description":"The user requests an illegal resource, such as a web page censored by a government."
},
{
"code":500,
"status":"Internal Server Error",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/500",
"description":"The server has encountered a situation it doesn't know how to handle."
},
{
"code":501,
"status":"Not Implemented",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/501",
"description":"The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD."
},
{
"code":502,
"status":"Bad Gateway",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/502",
"description":"This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response."
},
{
"code":503,
"status":"Service Unavailable",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503",
"description":"The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This responses should be used for temporary conditions and the Retry-After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached."
},
{
"code":504,
"status":"Gateway Timeout",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/504",
"description":"This error response is given when the server is acting as a gateway and cannot get a response in time."
},
{
"code":505,
"status":"HTTP Version Not Supported",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/505",
"description":"The HTTP version used in the request is not supported by the server."
},
{
"code":506,
"status":"Variant Also Negotiates",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/506",
"description":"The server has an internal configuration error: transparent content negotiation for the request results in a circular reference."
},
{
"code":507,
"status":"Insufficient Storage",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/507",
"description":"The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process."
},
{
"code":508,
"status":"Loop Detected (WebDAV)",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/508",
"description":"The server detected an infinite loop while processing the request."
},
{
"code":510,
"status":"Not Extended",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/510",
"description":"Further extensions to the request are required for the server to fulfill it."
},
{
"code":511,
"status":"Network Authentication Required",
"type":"Server error responses",
"link":"https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/511",
"description":"The 511 status code indicates that the client needs to authenticate to gain network access."
}
]
}

Reference Url, Type Of Response

Ref:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

https://tools.ietf.org/html/rfc7231)

Posted in Uncategorized, web | Tagged , | Leave a comment

Aazhi Mazhai Kanna -ஆழி மழை கண்ணா

Read in English http://godharangan.blogspot.in/2010/12/day-4-aazhi-mazhai-kanna.html

இந்தியா ஒரு புண்ணியபூமி .., தெய்வீக பூமி… கர்மபூமி … என்று உலக மக்களால் போற்றப்படும் நாடு இந்தியநாடு ….

சித்தர்களும், முனிவர்களும், ரிஷிகளும் , முனிகளும் வாழ்ந்த பூமி அண்ட சராசரங்களையும் அறிவியலே இல்லாத காலங்களில் .. அத்மஞ்சனங்களின் மூலம் எடுத்துச்சொன்னவர்கள் … நம் முனோர்கள் …வாழும் முறை, வாழ்வதற்க்கான வழி முறைகள் , வாழ்க்கை தத்துவம் , மருத்துவம், வானசாஸ்திரம் , கணிதம் , பொருளாதாரம் போன்ற எல்லா துறைகளிலும் வல்லவர்கள் … இந்தியர்கள் .,
5000 வருடங்களுக்கு முன்னரே … மழை எப்படி பொழிகிறது என்று , ஆண்டாள் , கோதை நாச்சியார் திருப்பாவையில் சொல்லி இருக்கிறார்

ஆழி மழைக்கண்ணா ஒன்றுநீ கைகரவேல்
ஆழிஉள் புக்கு முகந்துகொடு ஆர்த்துஏறி
ஊழி முதல்வன் உருவம்போல் மெய்கறுத்துப்
பாழியம் தோளுடைப் பற்பனாபன் கையில்
ஆழி போல்மின்னி வலம்புரி போல் நின்று அதிர்ந்து
தாழாதே சார்ங்க முதைத்த சரமழைபோல்
வாழ உலகினில் பெய்திடாய் நாங்களும்
மார்கழி நீராட மகிழ்ந்தேலோர் எம்பாவாய்.

விளக்கவுரை

மூன்றாம் பாசுரத்தில் நோன்பு நோற்பதால் கிடைக்கும் பலனைச் சொன்னார் ஆண்டாள். மும்மாரி பெய்து பசுக்கள் பாலால் இல்லம் நிறைத்து செல்வம் பெருகும் என்றவர், இந்தப் பாசுரத்தில் தாம் சொன்ன சுபிட்சத்துக்காக கண்ணனே கருணை மழையாகப் பொழிய வேண்டும் என்று வேண்டுகிறார்.
மழை மண்டலத்துக்குத் தலைவனாக விளங்கும் கண்ணனே! உன் கொடையில் எதையும் நீ ஒளிக்காமல் அருள வேண்டும். நீ செய்ய வேண்டிய பணி ஒன்றும் உண்டு. அது, நீ கடலினுள் புகுந்து, அங்கிருந்து நீரினை முகந்து கொண்டு பேரொலி எழுப்பி கர்ஜனை செய்து, ஆகாயத்தின் மேல் ஏறி, ஊழி காலம் முதலான அனைத்துக்கும் காரணனாக விளங்கும் எம்பெருமானின் திருமேனியைப் போலே கறுத்து, பெருமை பொருந்திய சுந்தரத் தோளுடையானும், நாபியிலே கமல மலர் கொண்டு திகழும் பெருமானின் வலக்கையிலே திகழும் சக்கரத்தாழ்வானாகிய திருவாழியைப் போலே ஒளிர்ந்து, இடது கரத்தில் திகழும் பாஞ்சஜன்யப் பெரும் சங்கினைப் போலே நிலை நின்று முழக்கி, உன் சார்ங்கம் ஆகிற வில்லில் இருந்து விரைந்து புறப்படும் அம்புகளைப் போலே, இந்த உலகத்தார் அனைவரும் வாழும்படியாகவும், கண்ணன் எம்மானுடன் கலந்து மகிழ நோன்பு நோற்கும் நாங்களும் உளம் மகிழ மார்கழி நீராட்டம் செய்யும்படி, தாமதம் ஏதுமின்றி மழை பொழிய வைத்திடுவாய்…- என்று கண்ணனை வேண்டுகிறார் ஆண்டாள். மழை எப்படிப் பொழிகிறது என்ற அறிவியல் நுட்பத்தைத் தம் பாசுரத்தில் புகுத்தி, அதற்குக் காரணன் கண்ணனே என்று கூறி, அனைவரும் அவனைப் பிரார்த்தனை செய்யப் பணிக்கிறார் ஸ்ரீஆண்டாள் நாச்சியார்!

Src:
http://godharangan.blogspot.in/…/day-4-aazhi-mazhai-kanna.h…

 

Posted in tamil, Uncategorized | Tagged , , , , , , , | Leave a comment

What happens on January 19, 2038?

On this date the Unix Time Stamp will cease to work due to a 32-bit overflow. Before this moment millions of applications will need to either adopt a new convention for time stamps or be migrated to 64-bit systems which will buy the time stamp a “bit” more time.

The last unix time stamp (epoch) in 32 bit is 2147483647 (Tue, 19 Jan 2038 03:14:07 GMT)

https://en.wikipedia.org/wiki/Year_2038_problem

 

What is the unix time stamp?
The unix time stamp is a way to track time as a running total of seconds. This count starts at the Unix Epoch on January 1st, 1970 at UTC. Therefore, the unix time stamp is merely the number of seconds between a particular date and the Unix Epoch. It should also be pointed out (thanks to the comments from visitors to this site) that this point in time technically does not change no matter where you are located on the globe. This is very useful to computer systems for tracking and sorting dated information in dynamic and distributed applications both online and client side.

Posted in maths, Techonlogy, Uncategorized, web | Tagged , , , , | Leave a comment

Decimal To different Base[2-9] Conversion

This program converts decimal number into different base number system.

Supports Binary (base2) to base9 conversion

package com.lp.mysample;
import java.math.BigInteger;
/**
* @author lperumalm This class converts number to different base system (base2
* – base9)
* <h3>Sample Test Data for 16</h3>
* <ul>
* </li>
* <li>decimal-base2 for number 16 is 10000</li>
* <li>decimal-base3 for number 16 is 121</li>
* <li>decimal-base4 for number 16 is 100</li>
* <li>decimal-base5 for number 16 is 31</li>
* <li>decimal-base6 for number 16 is 24</li>
* <li>decimal-base7 for number 16 is 22</li>
* <li>decimal-base8 for number 16 is 20</li>
* <li>decimal-base9 for number 16 is 17</li>
* </ul>
*/
public class ConvertDecimalToBase2TO9 {
public static void main(String[] args) {
decimal2Base(new BigInteger("12345678900000"));
}
private static void decimal2Base(BigInteger no) {
for (int i = 2; i < 9; i++) {
BigInteger value = BigInteger.ZERO, factor = BigInteger.ONE, x = no, j = BigInteger.valueOf(i);
while (x.compareTo(BigInteger.ZERO) > 0) {
value = ((x.mod(j)).multiply(factor)).add(value);
x = x.divide(j);
factor = factor.multiply(BigInteger.TEN);
}
System.out.println("decimal-base" + i + " for number " + no + " is " + value);
}
}
}

Sample Output

For Input 15

  • decimal-base2 for number 15 is 1111
  • decimal-base3 for number 15 is 120
  • decimal-base4 for number 15 is 33
  • decimal-base5 for number 15 is 30
  • decimal-base6 for number 15 is 23
  • decimal-base7 for number 15 is 21
  • decimal-base8 for number 15 is 17

For Input  12345678900000

  • decimal-base2 for number 12345678900000 is 10110011101001110011110011100010101100100000
  • decimal-base3 for number 12345678900000 is 1121201020100120220200022200
  • decimal-base4 for number 12345678900000 is 2303221303303202230200
  • decimal-base5 for number 12345678900000 is 3104232422244300000
  • decimal-base6 for number 12345678900000 is 42131305424333200
  • decimal-base7 for number 12345678900000 is 2412642301124415
  • decimal-base8 for number 12345678900000 is 263516363425440
Posted in maths, Program, technology, Techonlogy, Uncategorized | Tagged , , , , , , , , , | Leave a comment

Happy Pi Approximation Day

Today 22 July Pi Approximation Day

Pi Approximation Day is observed on July 22 (22/7 in the day/month date format), since the fraction 22/7 is a common approximation of π, which is accurate to two decimal places and dates from Archimedes

approx-pi-day

Good Article about PI approximation

http://www.huffingtonpost.com/2012/07/21/pi-approximation-day-_n_1693199.html

http://www.bendigoadvertiser.com.au/story/4044914/world-celebrates-the-ongoing-mystery-of-pi/?cs=82

Posted in maths, Uncategorized | Tagged , , | Leave a comment

Story behind – 153 A fascinating number

The 153 story

“There is an interesting story about Pythagoras that was told that demonstrates His remarkable powers. Pythagoras, in His travels, apparently one day came across some fishermen who were drawing up their nets which were filled with fish. Pythagoras told the fishermen that He could tell them the exact number of fish they had caught, which the fishermen thought to be an impossible task, given how many were caught in the nets. The fishermen said that if He was right they would do anything He said. They counted all the fish and Pythagoras was totally accurate in His estimate. He then ordered the fishermen to return the fish to the sea and for some mystical reason none of them died. Pythagoras paid the fishermen for the price of the fish and left for Crotona. Incidents like this caused Pythagoras’ fame to spread. During one of His lectures in Italy it was said that He gained 2000 disciples from that one lecture alone.” http://www.iamuniversity.ch/Pythagoras-and-Biosophy

In this story, though it is not mentioned in this excerpt, Pythagoras counted 153 fish. Take note of that number especially. The number 153 was most significant for being the denominator in the closest fraction known, at the time. Now we go to the story of Jesus and the fishermen in John 21:1-11.

“After these things Jesus manifested Himself again to the disciples at the Sea of Tiberias, and He manifested Himself in this way. Simon Peter, and Thomas called Didymus, and Nathanael of Cana in Galilee, and the sons of Zebedee, and two others of His disciples were together. Simon Peter said to them, “I am going fishing.” They said to him, “We will also come with you.” They went out and got into the boat; and that night they caught nothing. But when the day was now breaking, Jesus stood on the beach; yet the disciples did not know that it was Jesus. So Jesus said to them, “Children, you do not have any fish, do you?” They answered Him, “No.” And He said to them, “Cast the net on the right-hand side of the boat and you will find a catch.” So they cast, and then they were not able to haul it in because of the great number of fish. Therefore that disciple whom Jesus loved said to Peter, “It is the Lord.” So when Simon Peter heard that it was the Lord, he put his outer garment on (for he was stripped for work), and threw himself into the sea. But the other disciples came in the little boat, for they were not far from the land, but about one hundred yards away, dragging the net full of fish. So when they got out on the land, they saw a charcoal fire already laid and fish placed on it, and bread. Jesus said to them, “Bring some of the fish which you have now caught.” Simon Peter went up and drew the net to land, full of large fish, a hundred and fifty-three; and although there were so many, the net was not torn.”

Between the stories we see a few parallels. The one that strikes me the most is the number 153 and the role it played in the story. Both stories include fishermen, nets, fish, and the number 153. I see 2 possible theories to this parallel. It could be that the writer of John was using the number 153 as a “generic” term for “many fish”, since it was a common number at that time or, possibly, we have a writer using the pythagoras narrative to rewrite the story of Jesus as a means of proclaiming his divinity. This appeared to be a common phenomenon in the times of Jesus and after. I remain agnostic on the subject for now..Perhaps with more study I can come to a more solidified conclusion. Please share your thoughts and theories!

Vesica Piscis:

The vesica piscis is a shape that is the intersection of two disks with the same radius, intersecting in such a way that the center of each disk lies on the perimeter of the other.[1] The name literally means the “bladder of a fish” in Latin.

The Pythagoreans had a diagram of 2 intersecting circles, one above, one below, with the circumference of one touching the center of the other. The 2 circles represented the spiritual and the material domains. The “transcendental” region where the circles intersect resembles a fish shape-exactly as used as the symbol for Christianity. The Pythagoreans called this shape vesica piscis. The ratio of the height of this fish symbol to its length is 153 : 265, which is the nearest whole number to the square root of 3 and the controlling ratio of the equilateral triangle

 

440px-vesica_piscis_circles-svg

Vesica Piscis Src: wikipedia

The mathematical ratio of the width of the vesica piscis to its height is the square root of 3, or approximately 1.7320508… (since if straight lines are drawn connecting the centers of the two circles with each other and with the two points where the circles intersect, two equilateral triangles join along an edge). The ratios 265:153 = 1.7320261… and 1351:780 = 1.7320513… are two of a series of approximations to this value, each with the property that no better approximation can be obtained with smaller whole numbers.

pythagoras_vesica

Src: blog.world-mysteries.com

how we compared to our life

 

In Christian art, some aureolas are in the shape of a vertically oriented vesica piscis

440px-chalice_well_cover

The modern Cover of Chalice Well  Src:Wikipedia

 

Application behind Vesica piscis

The shape may be found in the topology of certain networks.

The vesica piscis is also used as proportioning system in architecture, in particular Gothic architecture. The system was illustrated in Cesare Cesariano‘s Vitruvius (1521), which he called “the rule of the German architects”.

Anyway, remember that first number-153. Now the stories of both Pythagoras and Jesus have them telling fishermen-who have failed to catch any fish all day-to cast their nets again. Miraculously, their nets come in full of fish. Pythagoras was said to have correctly predicted the exact number of fish caught. In his story, the mystic number is not revealed, but in the Gospel story of Jesus the number of fish caught is given-exactly 153!

Some More Interesting thing about 153

  • Another interesting feature of the number 153 is that it is the limit of the following algorithm:Take a random positive integer, divisible by three.
            Split that number into its base 10 digits.
            Take the sum of their cubes.
            Go back to the second step.
    An example, starting with the number 84:

{\begin{aligned}8^{3}+4^{3}&=&512+64&=&576\\5^{3}+7^{3}+6^{3}&=&125+343+216&=&684\\6^{3}+8^{3}+4^{3}&=&216+512+64&=&792\\7^{3}+9^{3}+2^{3}&=&343+729+8&=&1080\\1^{3}+0^{3}+8^{3}+0^{3}&=&1+0+512+0&=&513\\5^{3}+1^{3}+3^{3}&=&125+1+27&=&153\\1^{3}+5^{3}+3^{3}&=&1+125+27&=&153\end{aligned}}

153 is:

  • the smallest number which can be expressed as the sum of cubes of its digits:
    153 = 13 + 53 + 33
  • equal to the sum of factorials of number from 1 to 5:
    153 = 1! + 2! + 3! + 4! + 5!
    and
  • The sum of digits of 153 is a perfect square:
    1 + 5 + 3 = 9 = 32
    That’s a big one for me.
  • The sum of aliquot divisors of 153 is also a perfect square:
    1 + 3 + 9 + 17 + 51 = 81 = 92 Aliquot divisors of a number are all the divisors of that number excluding the number itself but including 1. It is seen that the sum of aliquot divisors of 153 is the square of the sum of the digits of 153.
    awesome
  • On adding the number 153 to its reverse,504 is obtained, whose square is the smallest square which can be expressed as the product of two different numbers which are reverse of one another:
    153 + 351 = 504

5042 = 288 x 882

Ref:

http://www.greatdreams.com/numbers/jerry/153.htm

http://www.abovetopsecret.com/forum/thread655755/pg1

Sacred Geometry – The Vesica Piscis

https://en.wikipedia.org/wiki/153_(number)

http://www.halexandria.org/dward097.htm

http://www.unexplained-mysteries.com/forum/topic/133442-pythagoras-and-jesus-parallel/

https://www.goodreads.com/book/show/30845427-kadhaiyil-kalandha-kanitham [Read 3rd lesson]

http://blog.world-mysteries.com/ancient-writings/christ-myth-hypothesis

http://scienceofwholeness.com/how-the-vesica-pisces-explains-creation-and-the-arrow-of-time/

 

 

Posted in math, maths, Numbers, Uncategorized | Tagged , , , | 1 Comment