jeffplummer.net rapport :   Visitez le site

Données techniques du jeffplummer.net

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 jeffplummer.net.Actuellement, hébergé dans United States et son fournisseur de services est Google Inc. .

the related websites

domaine	Titre
mappio.com	mind map library. 1000s of mind maps in freemind, mindmanager and other formats
salvagemind.com	salvage mind - total solution for human mind
mindandrun.com	mind and run : votre escape game à aix en provence - mind and run
piplos.org	piplos - a digital mind and nothing without a human mind
openingmind.org	opening mind – open your mind
ever-mind.fr	ever mind - un site d'eva matesanzever mind
brainmeta.com	brainmeta.com - neuroscience, consciousness, brain, mind, mind-brain, neuroinfor
syncmindglobal.com	sync mind - binaural beats reviews - sync mind
mindbent.net	mind bent - mind bent learn how to alter your reality
awakening-mind.org	what is awakening mind? | foundation for awakening mind
oom2.com	out of mind
strator-rh.com	la société - hr mind
jeffplummer.net	plummer's mind
brindelaurier.com	peace our mind
vitaminsmind.com	vitamins mind

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é GSE contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.

DNS

HtmlToText

entrepreneurship, rich internet applications, software architecture, agile development, ai, and more feb 23, 2013 intro to mathematics in similarity classifiers part 2 intro this article will provide an introduction to the mathematics of similarity classifiers, specifically jaccard, extended jaccard, and cosine. we will attempt to introduce the topics in layman's terms and provide examples that readers can play with and watch the results. while this intro series of articles will go into theory and formulas full of greek letters, they will first build upon simple explanations and real world examples. hopefully in reading this article you can gain an understanding of both the application and the math involved. the example for the first set of classifiers i'm stealing an example from the great book "programming collective intelligence" by toby segaran. but rather than focus on the code, this article will use the example to simplify and explain the math. the premise is that a store like amazon.com wants to recommend items a customer might like. in order to make a decision on what to recommend we can take two different approaches. we could find similar movie buyers, and recommend movies that those similar buyers like. this is akin to getting movie recommendations from a friend who has similar tastes as you. alternatively, we could try to classify how similar movies are to each other, and recommend similar movies to the movies that you already like. for example, one could argue batman is similar to superman because both are superhero movies, so we could recommend batman to buyers who purchase superman. for brevity this article is going to stick with only talking about the similarity of movie viewers rather than item similarity, but the algorithms are the same. click the link below to play with a simple app that calculates the similarity between movie viewers using the mathematics we will discuss in detail. read more >> posted by jeff plummer at saturday, february 23, 2013 16 comments: labels: machine learning , similarity classifiers jan 21, 2013 introduction to the math behind similarity classifiers – part 1 abstract this article provides an introduction to the world of similarity classifiers in a way that is simple and fun. we will attempt to introduce the topics in laymen's terms and provide examples that readers can play with and watch the results. while this intro series of articles will go into theory and formulas full of greek letters, they will first build upon simple explanations and real world examples. hopefully in reading this article you can gain an understanding of both the application and the math involved. introduction to similarity classifiers similarity-based classifiers estimate the similarity between *things*. once we know things are similar, we can begin to group them and make decisions based on that grouping. commercial businesses can make more money knowing that people who buy one type of item, are very often interested in "similar" items. doctors who can successfully treat a specific pathology with specific medications can often successfully treat "similar" patients with those same medications. and the list goes on and on. pandora: "is this song similar to 'linkin park' such that we ought to group it with the ‘link park’ radio station?" google news: "is this unknown web article similar to these other top news articles such that we ought to group them together in our news aggregator?" amazon: "is the movie 'speed 2' similar to the movie 'cinderella' and we should recommend it as a purchase to 'speed 2' buyers?" image organizer: "is this image similar to these other images in a collection, and thus we think this new image is of the same person?" read more >> posted by jeff plummer at monday, january 21, 2013 21 comments: labels: machine learning , similarity classifiers jul 11, 2012 arraycollection ‘source’ attribute vs listcollectionview ‘list’ attribute i recently stumbled upon an interesting problem that highlighted the difference between arraycollection ‘source’ attribute and the listcollection ‘list’ attribute. i was working through some code that was not paying close attention to how it re-wrapped collection data. in some cases a collection was created to wrap the ‘source’ of another collection as in figure 1. in other cases a new collection was created to wrap the ‘list’ of the original collection as in figure 2. the code was wrapping the data in new arraycollections in order to apply different sorting and filtering, which is an extremely common use for collection views, but was stumbling upon some interesting runtime results… not all of the collection views were updating with the collection changes. var ac1 : arraycollection = new arraycollection ( ) ; var ac2 : arraycollection = new arraycollection ( ac1 . source ) ; figure 1 – clone arraycollection using the ‘source’ attribute var ac1 : arraycollection = new arraycollection ( ) ; var ac2 : arraycollection = new arraycollection ( ) ; ac2 . list = ac1 . list ; figure 2 – clone arraycollection using the ‘list’ attribute how ‘source’ and ‘list’ relate and why it matters jumping into the flex sdk source code the setter method arraycollection.source creates a new arraylist around the original source to create the ‘list’ attribute of the new collection view. what this means is that depending on how your new collection view wraps the original data, you may end up with the same source, but different lists (see figure 3 below). figure 3 – possible relationships in related arraycollections read more >> posted by jeff plummer at wednesday, july 11, 2012 17 comments: labels: adobe flex , apache flex jul 10, 2012 why doesn't tweetmeme work anymore? ??? switching to twitter's own re-tweet button because tweetmeme doesn't work with blogspot anymore. posted by jeff plummer at tuesday, july 10, 2012 22 comments: feb 1, 2012 unit tests as a measure of code cleanliness i recently attended the 2011 adobe max conference and sat in on the unit testing adobe flex session by michael labriola of digital primates. i expected the session to be a repeat of what i already know and strongly believe. unit tests simplify testing, document your code, improve maintainability, blah blah blah. the aspect of the lecture that i found most fascinating was on writing clean code and using unit tests as a means to verify code cleanliness. my training regarding unit tests has been pretty informal. through experience i’ve found that when i write automated tests my bug count goes way down, and when i do have a bug i have a great starting point to isolate and fix issues. i’ve always understood the difference between unit, integration, and functional testing but never much cared because all 3 have the benefits mentioned above. the simple discovery, however, that being able to unit test your code in the strictest sense is a very good measurement as to the cleanliness of your code was pretty eye-opening. if your code base is only testable at the integration level, your code is probably too tightly coupled and does not have good encapsulation. read more >> posted by jeff plummer at wednesday, february 01, 2012 24 comments: labels: adobe flex , clean code , unit testing sep 13, 2011 a simple and effective agile process introduction whenever i hear other software leads complain about their waterfall-ish development process, i always ask why haven’t they tried something more agile. the most common answer i’ve heard back is that they don’t know where to begin. entire books are written on the subject of agile development, and it’s a pretty big sell to project management that you want drop everything and try something that seemingly requires chapters to describe. that type of change tends to make project management cringe. the truth is books are written about agile development because people want to make money selling books about agile development. agile development is phenomenally simple and you make mod

Analyse PopURL pour jeffplummer.net

http://www.jeffplummer.net/2013/02/intro-to-mathematics-in-similarity.html#more
http://www.jeffplummer.net/search/label/adobe%20flex
http://www.jeffplummer.net/2011/06/getting-started-with-rational-team.html#more
http://www.jeffplummer.net/2011/05/drawing-on-google-map-in-adobe-flex.html#more
http://www.jeffplummer.net/2011/09/simple-and-effective-agile-process.html#more
http://www.jeffplummer.net/search/label/agile%20process
http://www.jeffplummer.net/2011/09/tide-client-framework-part-ii-tide.html
http://www.jeffplummer.net/search/label/software%20architecture
http://www.jeffplummer.net/search/label/apache%20flex
http://www.jeffplummer.net/2011/06/graniteds-tutorial-intro-to-tide-client.html
http://www.jeffplummer.net/search/label/graniteds
http://www.jeffplummer.net/search/label/games
http://www.jeffplummer.net/search/label/clean%20code
http://www.jeffplummer.net/search/label/project%20management
http://www.jeffplummer.net/2012/07/arraycollection-source-vs.html

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: JEFFPLUMMER.NET
Registry Domain ID: 1769200047_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2017-03-12T12:33:12Z
Creation Date: 2012-12-27T16:16:47Z
Registry Expiry Date: 2017-12-27T16:16:47Z
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: 2017-08-17T05:57:33Z <<<

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 net.whois-servers.net

  ARGS domain =jeffplummer.net

  PORT 43

  TYPE domain
RegrInfo
DOMAIN

  NAME jeffplummer.net

  CHANGED 2017-03-12

  CREATED 2012-12-27

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

Erreurs

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