techtwaddle.co.in Report : Visit Site

Technical data of the techtwaddle.co.in

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host techtwaddle.co.in. Currently, hosted in United Kingdom and its service provider is Globalcity Telecom S.R.L. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called LiteSpeed containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

a tech twaddler.. vsts incident postmorten without comments taylor lafrinere from our vsts team published two root cause analyses which are really a good read. sometime we all hit that one issue which makes you pull your hair out :-) i still remember the caching bug we hit in my previous team, where cache read/write were messing up validity check with dd/mm and mm/dd, maybe i should write about it someday. here are rca links, preliminary postmortem complete postmortem written by march 5th, 2018 at 6:24 pm posted in uncategorized the case of curious characters with 2 comments we stumbled upon an interesting issue the other day at work. a was working on adding search feature to a table/grid of cells, consisting of multiple string and date fields. the implementation used a client side search utility provided by our client sdk, which internally used tries for indexing and searching on string tokens. the feature was working well overall, but strangely the search was not working on date fields in ie (v11). it worked fine on other browsers. so if you searched for a string like ‘3/23’, it would work in chrome and firefox, but not in ie o_o what is special about these date fields, we wondered, that makes this issue specific to ie? on a closer look, we found that the trie wasn’t getting properly constructed in ie. we jumped into the client sdk code, looked around but did not find anything suspicious, we also tried a bunch of other things like changing system date format, trying to enter date in a string field in another column and searching on it but the results didn’t really provide any clues. v then stepped in and looked at the part of sdk where the trie was getting built and found that it somehow was failing to add date fields to the index. on debugging further, v found that the date string contained characters we had not expected, it wasn’t a usual string, it had stuff in it that was failing the trie construction. how were the date fields getting added to the index? our implementation was calling tolocaledatestring() on the date object and passing the string off to the search utility to build the index. it turns out that tolocaledatestring() were returning different values in chrome vs in ie. here’s a small piece of code that demonstrates this, if you run this code in chrome and ie, this is what you’ll see. chrome ie (v11) what? chrome reports length of the string as 8, which is what you’d expect. ie has got its own characters to the party. turns out ie adds left-to-right markers in the string. the value 0x200e is the unicode code point for left-to-right mark . this marker gets added before every token in the date string, thus adding 5 characters to the string length. the answer on this stackoverflow thread sums up the issue nicely, any of the output of tolocalestring , tolocaledatestring , or tolocaletimestring are meant for human-readable display only if the intent is anything other than to display to the user, then you should use one of these functions instead: toisostring will give you an iso8601/rfc3339 formatted timestamp togmtstring or toutcstring will give you an rfc822/rfc1123 formatted timestamp gettime will give you an integer unix timestamp with millisecond precision written by april 4th, 2017 at 11:31 pm posted in uncategorized to patch or not to patch without comments i was reading this post on designing rest apis on dev.to , when i remembered an interesting discussion i had had a while ago when working on a feature. warning: this might be mostly rant. the feature in discussion here allowed the publisher of an extension to reply to reviews left by users on the extensions product page. the publisher could only create and edit a reply, delete had to be done via a support email to our team, but rest apis were available to delete a reply that required admin permissions. as you can notice, these nicely fall into crud operations. now, the reviews feature had already been implemented, modeled using rest. how would you model or design the new reply feature in terms of rest? do you consider the reply as a separate resource, and model crud operations on the new resource? do you expect someone to http get a reply only? does a reply make sense without the context of the review? treat the reply like a sub-resource with its own crud operations? or are you the kind that thinks of replies as a property of reviews? a review either has a reply or not. creating a reply would be like updating the review so you do it via a patch review call. editing a reply is pretty much same so that too is done via patch. in this case the patch payload has instructions on what to do for the server. if the payload says update-reply , you either create or edit the reply. if the payload says delete-reply then you delete the reply associated with that review. but is this scheme ugly? if you think of replies as a property, a call to get reviews for a product returns all the reviews and each review object has a reply object if one exists. do you think getting replies should be optional and done based on a request param? something like get /extensions/my-awesome-extension/review s?filteroption=includereplies we went with the latter approach. what are your thoughts on this? written by march 27th, 2017 at 11:22 pm posted in uncategorized ratings and reviews on vs marketplace! without comments we’ve enabled a rating and review system on vs marketplace for vsts and vscode extensions. until now, download count of an extension served as a proxy for estimating the quality of an extension but no more! you can see a 5 star rating on the extension on the marketplace homepage . note that rating and review was already available for visual studio extensions . this enables it for vsts and vs code extensions as well. hovering over the stars shows you the exact rating and the number of people who have rated this extension. clicking on the extension takes you to the details page, where we show the average rating of the extension and the number of ratings on the banner, if you notice carefully, you can see that that color of the stars on the banner will change between orang-ish or red-ish based on the background color on which it is rendered. this is done so that the stars have a nice contrast and can be seen clearly against the background. here’s an example: red stars on a light background and orange stars on a dark background, you can click on the stars to scroll down to the details section, the detailed section consists of, as you can probably guess, details of the reviews. you need to be logged-in to leave a review, you can use your microsoft account or any other aad backend account for this. the detailed section shows the picture and the display name associated with your profile. you can easily change this by clicking on your name at the top and then editing your profile details, the name and picture you set here will be used in the review details section. so you have the control to change this anytime. clicking on the ‘write a review’ button brings up the review submit dialog, (who’s excited about pink buttons! :-) you need to provide a rating, that’s mandatory. the submit button will be disabled until you select a rating. the review comment is optional and you can choose not to enter any text, though i recommend entering the text as it helps the developer get more details out of the review and figure out what you like/dislike about the extension. after you provide a rating and review comment, click on ‘submit’ and your review will magically appear in the details section! if you see a review that’s offensive or just plain spam, use the flag icon on the review to report it. we have three categories that show up currently, you can select the most relevant option while reporting a review. our team will run through the reported reviews and take appropriate action based on the content of the review. that’s it for now, stay tuned for more! you can read more about this here, https://blogs.msdn.microso

URL analysis for techtwaddle.co.in

http://techtwaddle.co.in/blog/2015/07/20/visual-studio-2015-and-net-4-6-released-and-more/#respond
http://techtwaddle.co.in/blog/tag/visual-studio/
https://www.techtwaddle.co.in/blog/wp-content/uploads/2015/07/image20.png
http://techtwaddle.co.in/blog/tag/net/
http://techtwaddle.co.in/blog/2011/09/
http://techtwaddle.co.in/blog/category/marketplace/
https://www.techtwaddle.co.in/blog/wp-content/uploads/2015/03/image1.png
https://www.techtwaddle.co.in/blog/wp-content/uploads/2015/07/clip_image001.png
http://techtwaddle.co.in/blog/tag/sonarqubeintellijcode-analysis/
http://techtwaddle.co.in/blog/2011/04/
http://techtwaddle.co.in/blog/2011/01/
http://techtwaddle.co.in/blog/tag/intellij/
https://techtwaddle.co.in/blog/wp-content/uploads/2017/04/image.png
http://techtwaddle.co.in/blog/2010/03/
https://www.techtwaddle.co.in/blog/wp-content/uploads/2015/07/image23.png

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Access to .IN WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the .IN registry database. The data in this record is provided by .IN Registry for informational purposes only, and .IN does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to: (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. .IN reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Domain ID:D414400000003033718-AFIN
Domain Name:TECHTWADDLE.CO.IN
Created On:09-Jan-2017 05:04:16 UTC
Last Updated On:10-Mar-2017 19:22:45 UTC
Expiration Date:09-Jan-2018 05:04:16 UTC
Sponsoring Registrar:Endurance Domains Technology LLP (R173-AFIN)
Status:CLIENT TRANSFER PROHIBITED
Reason:
Registrant ID:EDT_63488007
Registrant Name:Prabhu Kumar
Registrant Organization:N/A
Registrant Street1:#9, Lakshmi Nivas, AMS Layout, Vidayranyapura
Registrant Street2:
Registrant Street3:
Registrant City:Bangalore
Registrant State/Province:Karnataka
Registrant Postal Code:560097
Registrant Country:IN
Registrant Phone:+91.9885906076
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email:[email protected]
Admin ID:EDT_63488008
Admin Name:Prabhu Kumar
Admin Organization:N/A
Admin Street1:#9, Lakshmi Nivas, AMS Layout, Vidayranyapura
Admin Street2:
Admin Street3:
Admin City:Bangalore
Admin State/Province:Karnataka
Admin Postal Code:560097
Admin Country:IN
Admin Phone:+91.9885906076
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email:[email protected]
Tech ID:EDT_63488008
Tech Name:Prabhu Kumar
Tech Organization:N/A
Tech Street1:#9, Lakshmi Nivas, AMS Layout, Vidayranyapura
Tech Street2:
Tech Street3:
Tech City:Bangalore
Tech State/Province:Karnataka
Tech Postal Code:560097
Tech Country:IN
Tech Phone:+91.9885906076
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email:[email protected]
Name Server:IN.SOLIDHOSTING.PRO
Name Server:EU.SOLIDHOSTING.PRO
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned



  REFERRER http://whois.registry.in

  REGISTRAR INRegistry

SERVERS

  SERVER co.in.whois-servers.net

  ARGS techtwaddle.co.in

  PORT 43

  TYPE domain

DOMAIN

  HANDLE D414400000003033718-AFIN

  NAME techtwaddle.co.in

  CREATED 2017-01-09

  CHANGED 2017-03-10

  EXPIRES 2018-01-09

  SPONSOR Endurance Domains Technology LLP (R173-AFIN)

STATUS
CLIENT TRANSFER PROHIBITED

NSERVER

  IN.SOLIDHOSTING.PRO 103.27.232.40

  EU.SOLIDHOSTING.PRO 109.163.228.39

OWNER

  HANDLE EDT_63488007

  NAME Prabhu Kumar

  ORGANIZATION N/A

ADDRESS

STREET
#9, Lakshmi Nivas, AMS Layout, Vidayranyapura

  CITY Bangalore

  STATE Karnataka

  PCODE 560097

  COUNTRY IN

  PHONE +91.9885906076

  EMAIL [email protected]

ADMIN

  HANDLE EDT_63488008

  NAME Prabhu Kumar

  ORGANIZATION N/A

ADDRESS

STREET
#9, Lakshmi Nivas, AMS Layout, Vidayranyapura

  CITY Bangalore

  STATE Karnataka

  PCODE 560097

  COUNTRY IN

  PHONE +91.9885906076

  EMAIL [email protected]

TECH

  HANDLE EDT_63488008

  NAME Prabhu Kumar

  ORGANIZATION N/A

ADDRESS

STREET
#9, Lakshmi Nivas, AMS Layout, Vidayranyapura

  CITY Bangalore

  STATE Karnataka

  PCODE 560097

  COUNTRY IN

  PHONE +91.9885906076

  EMAIL [email protected]

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .