All about Java
Intels 80286, Java von Sun, P4 mit Prescott-Kern – Was geschah am 1. Februar? Jeden Tag wagt PC Games Hardware einen Blick zurück in die noch junge, aber bewegte Geschichte des Computers.
Intels 80286, Java von Sun, P4 mit Prescott-Kern – Was geschah am 1. Februar? Jeden Tag wagt PC Games Hardware einen Blick zurück in die noch junge, aber bewegte Geschichte des Computers.
As the blog title suggest I’ve uploaded a first release candidate for the QxWT 1.0.1.0 which is going to be released on about a month.
The most important new features coming with this release:
Beside this I am in need of a browser charting library and played around a bit with Raphael this weekend which also has a very tiny charting module which is released under MIT. Because of my QxWT-work I’m quite good now in writing JSNI-Wrappers and so I did that for Raphael. You can look at the result of this here.
The wrapper is released under EPL and LGPL and I guess QxWT will in cooperate this library in 1.0.1.0.
Twitter Weekly Updates for 2010-01-31 Neue Firmware für HW group HWg-STE Artikel zu Bacula in der Computerwoche Serie NSClient++ – Teil 2: Installation Jetzt Plätze zur Nagios Schulung im März sichern! CeBIT vom 02.-06. März 2010 – wir sind dabei! JConsole – Java Monitoring auf die Schnelle Weekly Snap: Nagios in Magna, Kempten, Saxony’s Public [...]
hallo ich suche ein javafähiges programm für mein samsung s8000jet und zwar ein program für powerpoint gibt es soetwas und wenn ja bitte wo. so das.
Homebrewcoder `PSPfreak2007´ hat sein Homebrew Zock’n Roll geupdatet. Zock’n Roll ist ein Würfelspiel mit anschaulichem Spielprinzip. Changelog: Added an update check while uploading or viewing scores Added an Easy Installer written in java by qop Fixed the joker function in field 1 Download
Eclipse 3.6 M5 is now available for download. There are lots of new and exciting features, like the ability to open and file directly from the command line. You can also use the synchronize view to compare patches:
Debug also introduced a few new features (like instance counts):
Check out all the new features in the New and Noteworthy.
Download the milestone:
http://download.eclipse.org/eclipse/downloads/drops/S-3.6M5-201001291300/index.php
or use p2 to upgrade to it:
http://download.eclipse.org/eclipse/updates/3.6milestones/
Hallo Also ich hab da ein Problem. Nachdem ich die Wasserwaage und das Spiel Avatar gelöscht habe, wurden das WaaserwageSymbol und das AvatarSymbol.
Hallo! Habe mit grosser Begeisterung angefangen Java-Apps auf meinem neuen Samsung S8000 zu installieren, hat bisher auch ganz wunderbar funktioniert,
Ich gebe zu, ich bin seit 2-3 Jahren ziemlich Apple-infiziert, mittlerweile auch beruflich. Vorher habe ich über Jahre an meinen PCs herumgebastelt, ja, ich habe auch mal exotische Rechner gehabt wie den Acorn Archimedes, der als RISC-Desktop ziemlich flink war. Am Preis änderte sich über die Jahre nicht viel, jeder neue Rechner kostet im Prinzip letztlich 3000 DM oder 1500 EUR. Was mich an Apple…
1. Frage ich hab mal ne Frage ist es möglich auf den Satio Java zu installieren weil ich auch ab und zu auf Seiten will wo Java vorrausgestzt wird. 2.F.
 Chip Online |
Neue Lücke: Internet Explorer gibt alle Dateien frei
Chip Online … bis CHIP wieder eine kurze Anleitung abgibt, um den Internet Explorer wieder sicher zu machen wie beim letzten mal, wo dann einfach kein Java mehr ging. … |
Wenn man den Scala-Interpreter mit scala -savecompiled closures2.scala aufruft, erhält man ein JAR-Archiv, in dem man sich die generierten Java-Bytecode-Dateien anschauen kann. In diesem Fall werden vier class -Dateien erzeugt. …
 Pocketbrain |
Amazon Kindle DX inoffizieller Qt Support
yellowTAB – Wir stecken unsere Nase überall rein (Blog) Als Sun damals Java auf den Markt brachte, sollte es die Welt erobern und auf jedem Betriebssystem laufen. Einmal eine Software in Java geschrieben, … Kommentar: Warum das iPad kein e-Book Reader istNetbook News (Blog) Alle 111 Artikel » |
I believe that there are significant deficiencies in the proposed websocket protocol and this paper looks at how they can be rectified.
The web socket protocol document has adopted an algorithmic specification style, so that rather than describing the structure of websocket data framing, the document describes an algorithm that parses websocket data framing. This raises esoteric questions like: is an implementation that parses websocket data framing using a different algorithm a compliant implementation or not? But a more practical problem with this style of specification is that the spec is impenetrable as it is full of text like:
Let /b_v/ be integer corresponding to the low 7 bits of/b/ (the value you would get by _and_ing /b/ with 0x7F). Multiply /length/ by 128, add /b_v/ to that result, andstore the final result in /length/.If the high-order bit of /b/ is set (i.e. if /b/ _and_ed with 0x80 returns 0x80), then return to the step abovelabeled _length_.
I challenge the reader to confirm that the client side framing and the server side framing are symmetric and implement the same data framing!
Rather than such verbose means, IETF specifications typically use the precise language of augmented Backus-Naur Form (ABNF RFC5234) to formally describe protocols in a way that is not open to confusion or mis-implementation. To illustrate the clarity possible, I’ve translated section 4.2 into BNF:
ws0-frame = sentinel-frame
/ length-framesentinel-frame = %x00-7F ; frame type
*( %x00-FE ) ; utf-8 data
%xFF ; the sentinellength-frame = %x80-FF ; frame type
frame-length
octet-data ; binary dataframe-length = unlimited-integer
unlimited-integer = *( %x80-FF ) %x00-7F
; concatenate 7 low order bits from each octet
; to form a binary integeroctet-data = *( %x00-FF )
; the number of octets is exactly the length determined
; by the frame-length
ws1-frame = frame-length
frame-type
octet-data
frame-type = 0×00 ; utf8 frame
/ 0×01-FF ; undefined binary frameframe-length = unlimited-integer
unlimited-integer = *( %x80-FF ) %x00-7F
; concatenate 7 low order bits from each octet
; to form a binary integeroctet-data = *( %x00-FF )
; the number of octets is exactly the length determined
; by the frame-length
An HTTP/1.1 connection may be closed by either end or by an intermediary as part of normal operation, leaving a degree of uncertainty about the delivery status of messages in the pipeline. Messages can be resent on another connection only if they are known to be idempotent (eg GET / HEAD methods). Similarly, a Websocket may be closed by either end or an intermediary as part of normal operation, leaving a degree of uncertainty about the delivery status of messages that have been sent. But Websocket has no knowledge of any message type, so it is unable to know that any messages are idempotent, thus it is unable to retransmit any messages on a new connection. Worse still, websocket has no concept of an idle connection, and thus an implementation will either keep connections open forever (DOS risk) or rick closing an in-use connection. Note also that the burden of handling disconnection and message retries falls to the application with websocket.
So if a connection closes, a websocket application does not know which messages sent have been recieved, short of acknowledging every message (which is a significant overhead and thus not practicable as a solution for all). However, if websocket can be improved with a mechanism to orderly close connections, then the delivery status of messages can be well known for normal operation and will only be uncertain if there is a real failure of a network or node. Orderly close requires a connection life-cycle to be defined and maintained by exchanging control messages between the end points:
ws2-frame = frame-length
frame-type
octet-dataframe-type = 0×00 ; utf8 frame
/ 0×01 ; control frame
/ 0×02-FF ; undefined binary frameframe-length = unlimited-integer
unlimited-integer = *( %x80-FF ) %x00-7F
; concatenate 7 low order bits from each octet
; to form a binary integeroctet-data = *( %x00-FF )
; the number of octets is exactly the length
; determined by the frame-length
This improvement creates a control frame type that will allow messages about the lifecycle of a connection to be exchanged. To gloss over the detail, the control messages will need semantics of closing and closed, so an end point or intermediary can know if it is safe to send a message and that once a connection has been orderly closed, it is safe to assume that all message sent previously have been delivered.
A common protocol technique to deal with this issue is to implement message fragmentation, where a single message is transmitted in several frames and the frames of unrelated messages can be interleaved on a single connection. Either a message ID or a channel (== virtual connection) ID is needed to determine which fragments are part of the same message. The following improvement adds fragmentation and a channel ID to websocket:
ws3-message = 1*(ws3-frame)
ws3-frame = frame-length
message-length
channel-id
frame-type
octet-dataframe-type = 0×00 ; control frame
/ 0×01 ; utf8 frame
/ 0×02-FF ; undefined binary frameframe-length = 0×00 ; last frame of message
/ unlimited-integer ; frame-lengthmessage-length = 0×00 ; unknown message length
/ unlimited-integer ; known message lengthchannel-id = unlimited-integer
unlimited-integer = *( %x80-FF ) %x00-7F
; concatenate 7 low order bits from each octet
; to form a binary integeroctet-data = *( %x00-FF )
; the number of octets is exactly the length determined
; by the frame-length
A message is terminated when all octets have been sent for a known message length, or when a zero length frame is sent for an unknown message length. Related messages are sent on the same channel id and are strictly ordered. The creation and orderly close of channel-ids can be coordinated by control frames sent on the channel. The implementations of the protocol end points will be responsible for fragmenting and interleaving messages. A simple endpoint may choose not to fragment messages sent, but should be capable of assembling fragmented messages received.
It is frequently desirable to aggregate (aka multiplexing) message streams from multiple clients and/or components into a single stream of messages, so that resources can be shared and/or load from a single source policed as a single entity. Luckily the machinery needed for multiplexing over a transport protocol is exactly the machinery needed from message fragmentation and channels. Thus the improvements already proposed can accommodate multiplexing.
Luckily there already exists a standard extensible system for describing content encodings, transport encoding, character sets and/or content types. The IETF standards for Mime Type are widely used by web protocols and have good mappings to existing software components that can encode, decode, compress, decompress, validate, sign and/or display an unlimited and growing family of media types.
Mime types and associated encodings are typically represented by 1 or more name value pairs of ISO-8859-1 strings (aka meta data). It would possible to extend websocket by replacing the fixed octect mapping of content encoding with a per message set of mime-type name value pairs. However, to do so would be to repeat another mistake of HTTP, namely to have verbose highly redundant meta-data transmitted with every message.
A more efficient and equally flexible solution is to associate meta-data fields such as mime type with a channel rather than with a message, so that the meta data need only be sent once and will apply to all subsequent messages in a channel, or until it is replaced by updated meta data:
ws5-message = 1* (ws5-frame)
ws5-frame = frame-length
message-length
channel-id
frame-type
octet-dataframe-type = 0×00 ; control frame
/ 0×01 ; meta-data name+value headers
/ 0×02 ; data frame
/ 0×03-FF ; undefined frameframe-length = 0×00 ; last frame of message
/ unlimited-integer ; frame-lengthmessage-length = 0×00 ; unknown message length
/ unlimited-integer ; known message lengthchannel-id = unlimited-integer
unlimited-integer = *( %x80-FF ) %x00-7F
; concatenate 7 low order bits from each octet
; to form a binary integeroctet-data = *( %x00-FF )
; the number of octets is exactly the length
; determined by the frame-length
5. Send the following bytes to the remote side (the server):
47 45 54 20
Send the /resource name/ value, encoded as US-ASCII.
Send the following bytes:20 48 54 54 50 2F 31 2E 31 0D 0A 55 70 67 72 61
64 65 3A 20 57 65 62 53 6F 63 6B 65 74 0D 0A 43
6F 6E 6E 65 63 74 69 6F 6E 3A 20 55 70 67 72 61
64 65 0D 0A
GET /resource name/ HTTP/1.1 CRLF
Upgrade: WebSocket CRLF
Connection: Upgrade CRLF
Other than proposing incremental improvements to websocket, I have also proposed an entirely new protocol. The Bidirectional Web Transfer Protocol (BWTP) is an IETF draft protocol designed to be a transport for the websocket API as well as useful for other web clients. BWTP and the improved websocket protocol are more or less semantically equivalent and the main differences are mostly stylistic.
Either approach significantly improves upon the current websocket proposal and provides a transport protocol that would truly be a step forward.
Portal für Java(TM), Enterprise Architekturen, SOA.
There is a jurisdictional issue brewing over the future of internet standards – I know because I’m stirring the pot. The dispute is between the WHATWG and the IETF regarding the specification process for the websocket protocol (which I have some concerns about, but none the less is supported by Jetty).
The IETF
is the body that has been responsible for developing and/or
standardizing the vast majority of protocols which run the internet:
HTTP, FTP, SMTP, etc. It has an open collaborative based process based
on working code and rough consensus and is overseen by the Internet
Society, a non profit organization with membership open to all.
The WHATWG
was formed in response to concerns about the W3C’s evolution of HTML
and has been instrumental in developing the HTML5 standards. It is
essentially a browser vendor consortium that is governed by an invitation only committee
and lead by a Google employee. While it’s process is conducted openly
and all are invited to participate, only the appointed editor has any
power in the actual decision making process. The editor is appointed by
the browser vendors.
The majority of the
WHATWG efforts have been about HTML5, and most welcome the advances
they are driving in the browsers. However, the websocket API and
protocol have also come out of the HTML5 work and specify a new
protocol that will run over ports 80/443, that will start off looking
kind of like HTTP, but is expressly not HTTP.
Making
the internet work well by producing quality standards is exactly the
mission statement of the IETF. So a new protocol running over port 80
is definitely something that falls within the scope of the the IETF
mission. The WHATWG were invited to submit their protocol as a IETF
draft document, which they did and the IETF after due process has
formed the hybi working group to ” take on prime responsibility for the specification of the WebSockets protocol”. This appears to have shocked
the WHATWG and they saying that they do not wish to relinquish
editorial control of the protocol. It appears they were hoping for a
rubber stamp from the IETF.
Meanwhile,
Google’s Chrome browser has started shipping with the websocket
protocol enabled and it is expected that other browser vendors in the
WHATWG consortium will soon follow. The argument has been made that
it’s “already shipping”, so it’s too late to make any significant changes to the protocol.
The
problem is that the protocol has been developed by only a fragment of
the internet industry, and essentially by a single company within that
fragment. There has been no consensus sought or obtained from the wider
internet community – ie servers, routers, bridges, proxies, firewalls,
caches, load balancers, aggregators, offloaders, ISPs, filters,
corporate security policies, traffic monitoring, billing, accounting,
shaping, application frameworks etc. etc. These communities and
vendors are waking up to a world where the traffic they expected over
port 80/443 aint what it used to be. Their products and services will
be broken, bypassed or at best co-opted for unintended usage. They had
no real voice in this change. Many would not have even realized that
the HTML5 effort was going to substantially change the wire protocol.
It is easy to present this state of affairs as a takeover of port 80 by Google so that they can get Wave
to work better. That google expect the rest of the industry to
scramble to make the changes necessary to allow websockets to tunnel
through the infrastructure unhindered by any concerns other than
connectivity to Google. I know that this characterization of the
situation will be taken as personally insulting to the individuals
involved, who I’m sure are acting in good faith and not as part of some
conspiracy. However, the power of group-think is significant and
individuals are greatly affected by the environment that they operate
in. Conflicts of interest are avoided by not by peoples best
intentions, but by not creating processes that are inherently
conflicted.
I don’t mean to be too
Machiavellian about this, but if the IETF does not assert is roll as
the primary internet standards body, then the outcome will essentially
be that a Google led consortium has taken over port 80. Note that
Google are also doing some great research on a HTTP replacement
protocol called SPDY, which
is showing some excellent promise. SPDY might be the way of the future,
but do we really want it to arrive by having google simply start
shipping it in Chrome? If we let port 80 be taken by websockets
without consensus, then could happen with HTTP as well (mwah ha ha ha)!
The
websocket protocol as specified by the WHATWG might indeed be
wonderful, but unless we follow due
process, we will not really know that it is. The IETF has a truly open
process based on rough consensus in which all are welcome to
participate. They have a proven track record and have overseen the
standards that have withstood the unprecedented growth in the
internet. The IETF are the natural body to oversee standardization of
internet protocols and there is no evidence that this task would be
better handled by a closed industry consortium lead by Google.
My
suggestion of how to break this impasse, is for the WHATWG to continue
to be the editor of the current specification and to push forward with
the deployment of 1.0, which essentially ignores intermediaries and
proxies anyway. In parallel, the IETF should continue with their
working group to develop the 1.1 specification based on 1.0, but with
an all-of-industry rough consensus.
Aloha… hab seit heute bzw. gestern mein HD2 und bin überglücklich. Funktioniert einwandfrei, aber jetzt bin ich doch an ein kleines Problem gestoßen.
TV Handy von FLY YING, Modell F006 mit WLAN, Dual-SIM, 3,2 Zoll Touchscreen Display und 9 MP Kamera.
|
Re[3]: bluescreen
Pro-Linux Das einzige, was auf meinem Desktop abschmiert sind gelegentlich bestimmte Java-Applets (ja hurra, sch*** Java VM für Linux..) Selbst Firefox stürzt nur … |
Lynn Gayowski, Wayne Beaton, Chris Aniszczyk,
Rüdiger Herrmann and Benjamin Muskalla.
On the other note, I would like to welcome everyone at Eclipse Planet. It’s a pleasure to be here.
Mit dem Programm dirhtml eine einfache .html Datei generieren. Diese Datei mit .jar und .jad in einen beliebigen Ordner auf dem Telefon kopieren. Im.
Fennec, die Firefox-Version für Nokias Maemo-Smartphone, und der Dienst Weave sind dem Beta-Stadium entwachsen.
Hi, Ich bin grade dabei Java zu lernen und hab eins noch nicht gecheckt: Wie kann ich zwischen Klassen kommunizieren? Genauer gesagt, in einer Hierarchie von Vererbung und Instanzierung ist ja klar wie die Infos ausgetauscht werden. …