documentroot.com Report : Visit Site

Technical data of the documentroot.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host documentroot.com. Currently, hosted in United States and its service provider is Server Pronto .

the related websites

matlan.com hackspc.com entrust.net alt-consulting.ca monitorix.org penguintutor.com 

HTTP Header Analysis

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

DNS

HtmlToText

www.documentroot.com search this site: view archive free blog commenter & counter memebot: free website hosting americans for approval voting 2002 wtc pics: aug 12 aug 16 aug 30 sep 11 sep 23 oct 24 shop with bitcoin at amazon yvette's weblog all sites by me rss for this site lo! in the east against the blazing shadow of a rising sun, there come four men striding in unison, each step a journey, against the terrible winds. tuesday, june 16, 2015 get block size bash posted 10:13 am probe for block size. useful when you've probably got no tools. like when trying to optimize sqlite paging at run-time. function block_size() {( [ "$1" ] && cd $1; echo 1 > block_size.tmp; ls --block-size 1 -s block_size.tmp | cut -f 1 -d ' '; rm block_size.tmp; )} [view/post comments] [digg] [del.icio.us] [stumble] wednesday, may 06, 2015 viral load posted 1:35 am quintiles put the poster i made up on their site: identifying viral load in tumors using nextgen sequencing . thanks kim! [view/post comments] [digg] [del.icio.us] [stumble] wednesday, august 06, 2014 gene therapies i want to see developed posted 10:58 am gene therapies i'd love to see developed/tested in my lifetime: ​1. daf-2 - downregulation increases lifespan in c.elegans next steps: rnai and/or crispr to cause daf-2 homolog (foxo3) downregulation in mice + tests on resulting phenotype. ​ ​2. pepck-c - beta-actin promoter linked to pepck gene shown to improve longevity, intelligence metabolism in mice. next steps: lentiviral transfection vector as a longevity vaccine (develop in mouse ageing model with human gene) ​ ​3. m-cat - mitochondrial targeted catalase : upregulation shown to improve cancer resistance and longevity next steps: develop transfection vector as a cancer vaccine (develop in mouse ageing model with human gene) ​ 4. has2 - molecular weight and production of hyaluron decreases over time. organisms with large amounts of hmwha live longer and resist cancer. next steps: test regular intravenous injection of hmwha in rat models of cancer and aging. develop gene therapy intervention to increase has2 expression. 5. tert - tert+ mice live longer, but also produce more tumors. has2, m-cat and pepck-c all interfere with tumorgenesis. the upregulation of tert while simultaneously increasing m-cat and has2 expression should have a strong synergistic effect. next steps: develop gene therapy intervention to increase tert expression, matching prior experiments, but combine with other interventions. [view/post comments] [digg] [del.icio.us] [stumble] tuesday, june 24, 2014 clustered object encoding 2.0 posted 1:38 pm without going into detail about of "the cloud" and the exaggerations and mysticism that accompany it, here's some definitions that it took me a while to truly understand: object storage: some manky, idiosyncratic api that allows developers to store "stuff". avoids dealing with things like partial writes, seeks, memory maps, etc. generally space wasteful by design. not a place you'd want to put anything you care about. yet, secretly, is probably the location of everything you care about. your bank probably keeps your pdf statements in something like this. block storage: like a horse, one can mount this kind of storage... but only for exclusive access. no shared, lockable access, no parallel reads. essentially it's the virtual hard drive for your virtual machine from which you derive your virtual paycheck. clustered storage: typically one of the above, but your data is now copied ad nauseum. someone probably didn't stripe it. the things you expect from clustered storage, like striped files, full posix support, parallel writes, and erasure coding don't work in your version of the software, but every whitepaper you read refers to them. posix, erasure coded, clustered, storage (peccs): 1. this is what you actually want if you run your own data center. used in a sentence: "wow, that guy's got peccs". 2. a mythical beast. 3. maybe some company named "nextemcapp" does it. maybe some guy names xavier in spain got it to work once, but then he got hired by [some big company] and nobody heard from him again. [view/post comments] [digg] [del.icio.us] [stumble] wednesday, june 11, 2014 variable length, zipf's law and density functions posted 9:17 am when coding, variables should be named based on both frequency and the length of their context. variables, structures and other constructs should have a name length that follows to zipf's law as it applies to word length and frequency . please glance at those references before continuing. when these laws of linguistic use are ignored, readability is demonstrably diminished. consider a variable, the hated "x", used 100 times in a file. if "x" is used 100 times in 40 lines of mathematical manipulation, such as in a digest function, this would be acceptable... the high frequency of use strictly precludes a longer name. if, however, it was spread out across 10000 lines of code, a far longer name would be needed. of course, suppose that function was embedded in 10k lines of code. does this change the freqency of x? no. one important rule is that, for the purposes of linguistic calculation, the frequency of any variables usage should be computed relative to the scope of it's use. as a demonstration, cluttering a short for i=1 to 10 ... loop with for iterationindex = 1 to 10, can cause code to be nigh unreadable. operation can often be obscured by foolish verbosity: for iterationindex = 1 to 10 countarray[iterationindex]=sizearray[iterationindex]*factorarray[iterationindex] + computedensity(histogram,iterationindex) versus for i = 1 to 10 countarray[i]=sizearray[i]*factorarray[i] + computedensity(histogram,i) likewise stuffing common prefixes on sets of variables in order to lengthen them can hide their meaning in a limited scope: for i = 1 to 10 wordsuffixcountarray[i]=wordsuffixsizearray[i]*wordsuffixfactorarray[i] + computedensityforwordsuffix(currentwordsuffixhistogram,i) it's clear that a minimum set of descriptive, distinct terms within the scope of use should, instead, be used. recently, software engineering pundits seem to take the stance that there is no such thing as a variable with too-long a name. this is false. numerous linguistic studies on readability, word length and frequency, bear that out and so, of course, does common sense. maximum clarity can be achieved in coding languages by using the same types of statistical distributions that occur in natural languages. [view/post comments] [digg] [del.icio.us] [stumble] friday, may 30, 2014 capricious job scheduling posted 12:16 pm using a perfectly fair scheduler, i launch 5 processes with the following pattern: iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc where 'i' is one second of i/o intensive operation, and 'c' is one second of cpu intensive operation. the result of a perfectly fair scheduler is that there will be periods of high i/o contention and high cpu contention, as the 5 processes are "fairly" switched between, and each keeps the pace with the other. using a more "capricious" scheduler, where processes may "get lucky" for a while, my processes will be staggered iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc lucky (goes first) iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc unlucky (goes last) iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc iiiiiiiiicccccccccccciiiiiiiiiiiiiiccccccccccccc it's clear that "everyone wins" when this method is chosen. my argument for "capricious" scheduling is that a system cannot know, in advance whether something will be an i or a c. programs can be profiled over time (modern o/s systems don't do this... but probably should), but most program execution paths vary to the point where profiling may be impra

URL analysis for documentroot.com

http://del.icio.us/post?url=http://www.documentroot.com/2015/06/get-block-size-bash.html&title=get
block
size
bash
http://www.documentroot.com/2015/05/quintiles-put-poster-i-made-up-on-their.html
http://del.icio.us/post?url=http://www.documentroot.com/2014/04/new-verison-of-bowtie-10.html&title=new
verison
of
bowtie-1.0
http://del.icio.us/post?url=http://www.documentroot.com/2015/05/quintiles-put-poster-i-made-up-on-their.html&title=viral
load
http://del.icio.us/post?url=http://www.documentroot.com/2014/06/variable-length-zipfs-law-and-density.html&title=variable
length,
zipf's
law
and
density
functions
http://www.documentroot.com/2014/06/variable-length-zipfs-law-and-density.html
http://www.documentroot.com/2014/06/buzz-words.html
http://digg.com/submit?phase=2&url=http://www.documentroot.com/2014/06/variable-length-zipfs-law-and-density.html&title=variable
length,
zipf's
law
and
density
functions
http://www.documentroot.com///rss.xml
http://www.stumbleupon.com/submit?url=http://www.documentroot.com/2014/04/latest-printable-firearm-kit-from.html&title=latest
printable
firearm
kit
from
defdist
http://digg.com/submit?phase=2&url=http://www.documentroot.com/2014/04/latest-printable-firearm-kit-from.html&title=latest
printable
firearm
kit
from
defdist
http://www.documentroot.com/2015/06/get-block-size-bash.html
http://www.documentroot.com/2014/02/bitkin-mojolicious-and-liteapi.html
http://www.documentroot.com/comment.html?b=1&i=6581320600760961564&t=viral
load
http://www.documentroot.com/comment.html?b=1&i=283384149796382539&t=get
block
size
bash

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;

Domain Name: DOCUMENTROOT.COM
Registry Domain ID: 20442923_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2017-06-26T03:31:47Z
Creation Date: 2000-02-22T19:29:20Z
Registry Expiry Date: 2023-02-22T19:29:20Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
Name Server: DNS5.NAME-SERVICES.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-04-24T15:51:11Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR eNom, Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =documentroot.com

  PORT 43

  TYPE domain

DOMAIN

  NAME documentroot.com

  CHANGED 2017-06-26

  CREATED 2000-02-22

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS1.NAME-SERVICES.COM 162.88.61.23

  DNS2.NAME-SERVICES.COM 162.88.60.23

  DNS3.NAME-SERVICES.COM 162.88.61.39

  DNS4.NAME-SERVICES.COM 162.88.60.39

  DNS5.NAME-SERVICES.COM 162.88.61.41

  REGISTERED yes

Mistakes

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