0xcafefeed.com rapport :   Visitez le site

Données techniques du 0xcafefeed.com

Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations. Notre service GeoIP a trouvé l'hôte 0xcafefeed.com.Actuellement, hébergé dans United States et son fournisseur de services est New Dream Network LLC .

the related websites

domaine	Titre
0xcafefeed.com	0xcafefeed

Analyse d'en-tête HTTP

Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé Apache contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.

DNS

HtmlToText

skip to content skip to menu thoughts on java™, java ee™ and web application development search -- home about may 13 2008 where was this class loaded from?! tags: class loading , core , java — rajiv @ 9:54 am utc there are many ways to figure out where a class is being loaded from. naveen uses the -verbose flag of the jvm to figure out where a class is being loaded from. if you are using pramati server, then you can use the command: who_load_me to find out which classloader loaded the class, the classloader hierarchy and where the class was loaded from. another way to find out where a class was loaded from is by using the getcodesource method, like so: public static void which(class aclass) throws exception { system.out.println(aclass.getprotectiondomain().getcodesource().getlocation()); } i used to use this so much that ravi finally decided to check it into cvs. thanks buddy! lot of people wondered why i always called it which , it is in memory of the unix command which , which would tell you the directory in the path variable from which the shell was picking up the exectuable from. and if you are coming for an interview and give this as the answer to my question, you better be able to explain what a protection domain is and when/by-whom is the codesource set. update: i was inspired to blog about this after i spoke with deepak about this. i didn’t know he had a blog and he had blogged about the same topic too! comments (2) apr 12 2008 moved out of blogger tags: blogger , wordpress — rajiv @ 11:05 am utc when i first setup this blog, i chose blogger because it would let me publish (using sftp) to a server at my alma . this way neither was my data locked into any blogging service nor did i have to install any software on the server. for the past six months or so i have been having serious problems with blogger. it was not able to publish my posts or the comments i was receiving on them to the server. all attempts to get in touch with the folks at blogger were in vain and finally i decided to move out. the blog is now hosted at http://www..com . the old url redirects to this site. i am running wordpress . let me know if you have any comments on the design or issues with commenting or any other suggestions. comments (0) mar 06 2008 chasing the cause for performance degradation tags: debug , image resize , java , native , performance — rajiv @ 5:14 am utc spoiler: the last three pictures speak more than the thousand odd words that precede them day before: too many issues resizing photos in java. takes too much memory, takes too long, runs out of mem on mac. a quick comparison with imageresizer powertoy shows that the java code is taking too much memory and time. the difference is an order of magnitude higher on v’s machine which is slightly older and has lesser memory. yesterday (and day before): implement a photo resize server using gdi+ . go to bed happy that mem consumption is low, speed is very good and all kinks in passing around utf-8 filenames between java and vc++ have been ironed out. noon: j integrates the new resizer into the code base. 2pm: j verifies perf is 4 times better 6pm: code is checked in … waiting for integration build 8pm: leave for home 10pm: receive an e-mail, integration build ready .. start downloading with the hope of gloating in the perf gains 10.30pm: installation started … baby crying … unplug the laptop move closer to baby … play with the baby and complete the installation … start the test case in background 10.35pm: no sign of test completing … should have finished 2mins ago 10.40pm: suspect some “first time” bug, run the test case again … 10.46pm: no luck … still pathetic perf … does not match what i saw in the morning 10.50pm: pissed … shoot of a mail to j … “dood, did you checkin the integration … i see no diff in perf … 10.55pm: no reply … shall i wait till morn … 11:00pm: let me try to recreate morning’s perf numbers … run the main method on java wrapper for the resizer … the same run which took 2mins in the morning is taking 6mins … as bad as the java resizer …damn .. 11:10pm: wtf?!! 11:11pm: maybe i messed up the java wrapper … run the main method on exe resizer … 11:18pm: just as bad … three times slower than what it was in the morn … 11:20pm to 12:05am: make many runs trying to change some code in the exe … nothing seems to improve perf 12:05am: low battery alert … curse the laptop … can’t run even a few hrs without power 12:07am: make some more changes to c++ code … build … run … 12:09am: by joe! done in 2mins instead of 6!… damn thing … why is this small change causing the whole thing to be 3 times slower … do some googling … 12:10am: undo the changes … recompile and run … see if it becomes slow again … 12:09am: thighs are burning … prop up the laptop 12:12am: hain?! done in 2mins … wtf … it was taking 6mins just a few mins ago … 12:15am: rollback all the changes … recompile … run … 12:17am: done in two mins … wtf … how can this be … check the logs for the timining … it was taking 6mins till a few mins ago … and the whole thing is back to 2mins now … no changes done … desperate to blame it on something … maybe anti virus was running earlier (should i check the anti virus logs?)… maybe the windows kernel has cached the files now (should i restart the laptop and see?) … maybe it became slow when i was running on battery … 12:18am: is that really possible … will my cpu run slow if it is running out of power … 12:18am: or will it be slow if it is running on battery … to save power 12:19am: hain … what a joke … laptop can’t be so smart … it was just a coincidence … i plugged in the power and it became faster … 12:19am: there are no coincidences in this business … unplug the power … run the test … 12:22am: no sign of ending it really is slow 12:25am: back to 6mins for the test 12:25am: … can’t be … really i mean … can the laptop be so smart … what was that thing that showed clock speed … cpu-z … google: cpu-z … download … run … wow! it is true … clock speed has been reduced to 598mhz instead of 1.6ghz 12:25am: ok … now connect the power and see … there goes my theory … still 598mhz 12:25am: hmmm … maybe it realized though it is powered, i am not running any cpu intensive task …. could it really really that smart … nyaaah … 12:26am: start the test with power still connected … run cpu-z … whoa! 1.6ghz … more googling reveals, this is intel speedstep tm technology at work. it can be enabled/disabled from bios. a quick intro at bay wolf. implementation details at intel. now i have to locate some java api to detect if the cpu is running at a lower clock speed so i can warn the users to power up! update june 05, 2008: i was wrong in suspecting my dying battery . replacing it with a brand new one didn’t help . long long ago i was bugged by the fact that the screen would go blank when i was reading some content heavy websites. i opened up the power management dialog, noticed that the default power scheme used to switch off the monitor too soon when running on battery. so i decided to change the power scheme to presentation. there is no indication that this setting does anything other than affect: monitor, hard disc and system standby. however, following alexander’s suggestion when i changed the power scheme from “presentation” to “home/office desktop”. i notice that the clock speed behaves the same when on battery or power: when there is no cpu intensive task, it runs on low clock speed and when there is a cpu intensive task it runs at the rated clock speed. i wish xp warned me or atleast hinted in some fashion that the power scheme would affect the clock speed. *sigh* comments (6) dec 31 2007 yahoo! messenger archive file format tags: desktop , file format , search , wds , ymessenger — rajiv @ 8:46 pm utc the first step to get my yahoo! messenger (ymessenger) conversations into windows desktop search is to decode the conversations stored in ymessenger archive files. if you enable message archiving, ymessenger saves all th

Analyse PopURL pour 0xcafefeed.com

http://www.0xcafefeed.com/tag/performance/
http://www.0xcafefeed.com/2007/06/
http://www.0xcafefeed.com/2007/06/why-do-catch-clauses-need-to-be-ordered/#comments
http://www.0xcafefeed.com/2008/04/moved-out-of-blogger/#respond
http://www.0xcafefeed.com/2008/04/moved-out-of-blogger/
http://www.0xcafefeed.com/wp-content/uploads/2007/12/parser.java
http://www.0xcafefeed.com/2007/12/21/addicted-to-search/
http://www.0xcafefeed.com/tag/java/
http://www.0xcafefeed.com/tag/desktop/
http://www.0xcafefeed.com/wp-content/uploads/2007/12/main.java
http://www.0xcafefeed.com/page/2/
http://www.0xcafefeed.com/2005/09/why-is-finalize-method-protected
http://www.0xcafefeed.com/2007/07/neal-gafters-proposal-for-constructor/#comments
http://www.0xcafefeed.com/2004/07/
http://www.0xcafefeed.com/#comment-123

Informations Whois

Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;

Domain Name: 0XCAFEFEED.COM
Registry Domain ID: 1448128575_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.dreamhost.com
Registrar URL: http://www.DreamHost.com
Updated Date: 2017-04-13T07:14:31Z
Creation Date: 2008-04-12T08:39:42Z
Registry Expiry Date: 2018-04-12T08:39:42Z
Registrar: DreamHost, LLC
Registrar IANA ID: 431
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.DREAMHOST.COM
Name Server: NS2.DREAMHOST.COM
Name Server: NS3.DREAMHOST.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-13T20:24:01Z <<<

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 DreamHost, LLC

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =0xcafefeed.com

  PORT 43

  TYPE domain
RegrInfo
DOMAIN

  NAME 0xcafefeed.com

  CHANGED 2017-04-13

  CREATED 2008-04-12

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

NSERVER

  NS1.DREAMHOST.COM 64.90.62.230

  NS2.DREAMHOST.COM 208.97.182.10

  NS3.DREAMHOST.COM 66.33.205.230

  REGISTERED yes

Erreurs

La liste suivante vous montre les fautes d'orthographe possibles des internautes pour le site Web recherché.