INSERT INTO sites(host) VALUES('goessner.net') 1045: Access denied for user 'www-data'@'localhost' (using password: NO) goessner.net Estimated Worth $347,094 - MYIP.NET Website Information
Welcome to MyIP.net!
 Set MYIP as homepage      

  
           

Web Page Information

Title:
Meta Description:
Meta Keywords:
sponsored links:
Links:
Images:
Age:
sponsored links:

Traffic and Estimation

Traffic:
Estimation:

Website Ranks

Alexa Rank:
Google Page Rank:
Sogou Rank:
Baidu Cache:

Search Engine Indexed

Search EngineIndexedLinks
 Google:
 Bing:
 Yahoo!:
 Baidu:
 Sogou:
 Youdao:
 Soso:

Server Data

Web Server:
IP address:    
Location:

Registry information

Registrant:
Email:
ICANN Registrar:
Created:
Updated:
Expires:
Status:
Name Server:
Whois Server:

Alexa Rank and trends

Traffic: Today One Week Avg. Three Mon. Avg.
Rank:
PV:
Unique IP:

More ranks in the world

Users from these countries/regions

Where people go on this site

Alexa Charts

Alexa Reach and Rank

Whois data

Who is goessner.net at whois.1and1.com

Domain Name: goessner.net

Registry Domain ID: 65998974_DOMAIN_NET-VRSN

Registrar WHOIS Server: whois.1and1.com

Registrar URL: http://1and1.com

Updated Date: 2016-03-04T07:10:15.000Z

Creation Date: 2001-03-03T06:39:24.000Z

Registrar Registration Expiration Date: 2017-03-03T06:39:24.000Z

Registrar: 1&1 Internet SE

Registrar IANA ID: 83

Registrar Abuse Contact Email: abuse

Registrar Abuse Contact Phone: +1.8774612631

Reseller:

Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited

Domain Status: autoRenewPeriod https://www.icann.org/epp#autoRenewPeriod

Registry Registrant ID:

Registrant Name: Stefan Goessner

Registrant Organization:

Registrant Street: Semperstr. 7

Registrant City: Dortmund

Registrant State/Province:

Registrant Postal Code: 44269

Registrant Country: DE

Registrant Phone: +49.231445438

Registrant Phone Ext:

Registrant Fax:

Registrant Fax Ext:

Registrant Email: stefan@goessner.net

Registry Admin ID:

Admin Name: Stefan Goessner

Admin Organization:

Admin Street: Semperstr. 7

Admin City: Dortmund

Admin State/Province:

Admin Postal Code: 44269

Admin Country: DE

Admin Phone: +49.231445438

Admin Phone Ext:

Admin Fax:

Admin Fax Ext:

Admin Email: stefan@goessner.net

Registry Tech ID:

Tech Name: Hostmaster EINSUNDEINS

Tech Organization: 1&1 Internet AG

Tech Street: Brauerstr. 48

Tech City: Karlsruhe

Tech State/Province:

Tech Postal Code: 76135

Tech Country: DE

Tech Phone: +49.7219600

Tech Phone Ext:

Tech Fax: +49.72191374248

Tech Fax Ext:

Tech Email: hostmaster@1und1.de

Nameserver: ns11.schlund.de

Nameserver: ns12.schlund.de

DNSSEC: Unsigned

URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/

>>> Last update of WHOIS database: 2016-04-21T04:12:35Z <<<



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

Front Page Thumbnail

sponsored links:

Front Page Loading Time

Keyword Hits (Biger,better)

Other TLDs of goessner

TLDs Created Expires Registered
.com
.net
.org
.cn
.com.cn
.asia
.mobi

Similar Websites

More...
Alexa鏍囬

Search Engine Spider Emulation

Title:stefan.goessner
Description:
Keywords:
Body:
stefan.goessner
lt;stefan.goessner/ gt;
Mechanik, das Web und der ganze Rest
| Home | Lehre | Download | Info |
1.9.07
#35;
JSONPath - XPath for JSON
Here and there on the web we can find a discussion or solution for something like XPath for JSON. Despite the fact, that JSON structures can be processed by the C family of programming languages quite easily, there should be a benefit in having some kind of XPath4JSON.
So I was thinking about a suitable path expression syntax for addressing portions of any JSON structure. Those path expressions should
be naturally based on C language family characteristics.
cover only essential parts of XPath 1.0.
As a result here is JSONPath, wich is a dual thing. Primarily JSONPath is a path expression syntax, which can select parts of JSON structures in the same way as XPath expressions select nodes of XML documents. Such an expression may look like
$..book[2].title
and is quite similar to its XPath counterpart
//book[3]/title
Currently there is a small set of nine JSONPath syntax elements, which allows the construction of sophisticated path expressions.
Furthermore JSONPath is a lightweight tool implemented in Javascript and PHP for accessing JSON structures on the client and the server.
You can download
jsonpath.js
jsonpath.php
for free and read more about it.
Update:
Atif Aziz came up with a C# port of JSONPath in a very short time (jsonpath.cs). Thanks for that.
JSON
XPath
Javascript
PHP
C#
Labels: Javascript, JSON, PHP, XPath
3 comments
2.6.06
#35;
Converting Between XML and JSON @ XML.com
xml.com has published my article Converting Between XML and JSON.
The conversion scripts are here.
Update:
There are some bug fixes and updates available to xml2json.js and json2xml.js. Read more in the download section.
XML
JSON
15 comments
25.5.06
#35;
Towel Day
Don't forget #8230; today is towel day.
The reason why this date was chosen, is obviously a numerical one:
2516 + 516 = 4210
TowelDay
0 comments
24.5.06
#35;
XTech 2006
I had the opportunity to attend the web technology conference XTech 2006 in Amsterdam last week.
All in all it was a great conference, starting with an Ajax Developers' Day chaired by Simon Willison of Yahoo!.
What followed were 3 days of interesting sessions and conversation with nice people mostly about technical stuff.
Finally the real highlight was the closing note "Javascript 2 and the Future of the Web" of Brendan Eich, the inventor of javascript.
XTech2006
0 comments
7.4.06
#35;
Web Component Model
After reading the article about ALE - Ajax Linking amp; Embedding over at Ajaxian I was thinking a while about the potential of this concept. I wasn't so much drawing the parallel to OLE, but stepped down a level to the concept of Microsoft's COM-Programming.
Basically COM-Interfaces allow design by contract via immutable interfaces and demand separation of interface and implementation. Given this, COM-components implementing identical interfaces are arbitrarily interchangeable.
Considering an inline web component, we might start with a clearly defined document fragment. A very good example for that is the open standard microformat XOXO, which is
A simple, open outline format written in standard XHTML and suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.
Given a specific XOXO structure, we could easily define two different presentations via CSS, which might be even switched by the user.
But what's about behaviour. XOXO components might be
collapsable/expandable (example),
resortable via drag and drop (example by Tim Taylor).
collapsable/expandable and editable (example by Les Orchard).
So if there would be a standardized object interface #8211; perhaps defined alongside with the microformats specification, we rather did a big step forward to a truely reusable, implementation independent inline web component. The interface definition of a collapsable XOXO element might look somewhat like:
interface XOXOCollapsableElement: Element {
void collapseItem(bool collapse);
void forEachItem(Function callback);
NodeList filterItems(Function callback);
...
};
There might be another interface for an editable XOXO element.
interface XOXoEditableElement: Element {
...
};
Now as a user i could download a specific XOXO object implementation, which implements either both interfaces or merely the XOXOCollapsableElement interface.
I believe, the long term benefit is worth the effort of agreeing to common interfaces for heavily reused inline web components.
Ajax
DOM
Microformats
Javascript
0 comments
2.3.06
#35;
Das wissenschaftliche Web
Der CSS Krieger George Chavchanidze kritisiert die gegenw盲rtigen Webstandards aus der Sicht eines Wissenschaftlers 鈥β
颅
Being emerged in European Centre for Nuclear Research (CERN), world wide web quickly evolved into entertainment oriented media and left many scientists disappointed. Web standards were science unfriendly and embedding complex mathematical formulae in web pages was far from being easy.颅
颅
鈥 und spricht mir damit aus der Seele. Es zeichnet sich speziell bei der Darstellung mathematischer Formeln keine allgemeine Einigung auf einen gemeinsamen Markup Standard ab; nicht zuletzt wegen individueller Vorlieben.颅
颅
Some dislike angle brackets some curly ones, some want to have self contained markup, some want to integrate math oriented markup with the rest of webstandards, some want to code pages manually, some think that what they see is what they get, some prefer to have clear hierarchical structure, some vote for drastically abridged Unicode based notations颅
颅
Trotz dieser gegenw盲rtig "verr眉ckten" Verh盲ltnisse sieht er einen nat眉rlichen Ausweg einhergehend mit der Weiterentwicklung 鈥 und Implementierung 鈥 von CSS (inline-blocks, inline-tables,鈥) und der Unterst眉tzung mathematischer Unicode-Bereiche. Hierbei haben offensichtlich die Browser Opera und Safari die Nase vorn.颅
Flankiert wird dieser Trend aus seiner Sicht durch clientseitige Webanwendungen zur Erstellung/Darstellung mathematischer Formeln. Ich freue mich, dass er in diesem Zusammenhang neben颅
jsMat, AsciiMathML und HMath auch Wiky erw盲hnt.
Math
CSS
0 comments
2.3.06
#35;
Math Is Easy ...
颅
from: Phantomakos颅
via: technorati
4 comments
25.2.06
#35;
WikyBloggerBox
As a proof of concept to combine Blogger with a pure clientside Wiki/HTML converter, I implemented WikyBloggerBox. In fact it is the modified BloggerBox and WikyBox, which works on top of Blogger's Atom API for remote communication and Wiky.
Some noteworthy points are:
conversion from/to Wiki syntax to/from HTML is performed clientside. So Blogger only sees validating XHTML.
The HTML code create depends only minimally on internal CSS #8211; as long as no math formulas are used. So this solution is supposed to be friendly to weblog readers.
Wiky supports a simplified LaTeX markup to create cross-browser math formulas purely in HTML/CSS.
Blogger
Wiki
Math
0 comments
21.2.06
#35;
Wiky: A Clientside Wiki/Html Converter
Wiky is a bidirectional Wiki markup to HTML converter written in javascript.
So there is no need for the web server to convert or even store wiki text, just plain HTML #8212; yes, I like smart clients. Besides converting wiki markup, Wiky also can do syntax highlighting and translate LaTeX style math formulas to HTML+CSS.
In fact Wiky + inplace editing is the way I am adding content to my web pages.
[ read more ...]
Wiki
Math
Javascript
9 comments
3.2.06
#35;
JSONT - Transforming JSON
In XML we can transform documents by another XML document containing transformation rules (XSLT) and applying these rules using an XSLT-processor.
Adopting that concept I have been experimenting with a set of transformation rules written in JSON.
Now in analogy to XML/XSLT the combination JSON/JSONT can be used to transform JSON data into any other format by applying a specific set of rules.
Read more ...
Json
5 comments
raquo; Search ..
input
input
input
Web
input
goessner.net
input
input
input
input
input
input
input
input
input
input
input
raquo; Inhalt ..
raquo; letzte Eintr盲ge ..
raquo; backlinks ..
technorati.com
bloglines.com
search.blogger.com
icerocket.com
blogpulse.com
raquo; delicious ..
raquo; Blogroll ..
Slashdot
The Daily WTF
mozillaZine feedHouse
Ajaxian
Read/WriteWeb
json at Yahoo! Groups
Tales from the Smart Client
ecmanaut
XML.com
Math News from Mathforge.net
CSS Warrior
Jens Meiert - Publikationen
BildungsBlog
Das E-Business Weblog
raquo; Lizenz ..
Sofern nicht ausdr uuml;cklich etwas anderes angegeben ist, gelten f uuml;r die Inhalte auf diesen
Seiten die Bedingungen der
(cc) Creative Commons License
(c) 2005 Stefan G ouml;ssner

Updated Time

Updating   
Friend links: ProxyFire    More...
Site Map 1 2 3 4 5 6 7 8 9 10 20 30 40 50 60 70 80 90 100 110 120 130 140 150 160 170 180 190 200 250 300 350 400 450 500 550 600 610 620 630 640 650 660 670 680 690 700 710 720 730 740 750
TOS | Contact us
© 2009 MyIP.cn Dev by MYIP Elapsed:54.113ms