Every time someone visit a site a flash light on the map.

Everyone can subscribe to this service: just put a link in your homepage to see the real time traffic of your site on a world map.
The collected data of all the participating websites will show on the collective map.

Populate - Real time site traffic
See my web traffic

Direct (P2P) communication between Flash players.

Every flash application will be able to connect to another without going through a server, saving bandwidth and lowering latency.
A Flash Media Server will be required to establish the connection between players.

UDP communication with a server

The next version of Flash Media Server (and maybe of Red5) will allow audio and video streaming from and to the flash player over the UDP, which is a more efficient way to deliver low latency packets.
Applications like Skype and the majority of multiplayer games already use that with obvious advantages.

Further informations:
RTMFP FAQ
Flash Player 10 Release notes
UDP Wikipedia entry

haxeVideo is an opensource video streaming server entirely written in haXe
Features include :

* FLV streaming using RTMP protocol
* Webcam and Microphone recording to FLV file
* Live streaming for web conferencing
* light and fast scalable server
* only 50 KB of server source code : modify whatever you need !

Finally the multiuser/conferencing thing is taking place?
We will ever see affordable (T)RTMP hosting services?

PS: This can be the right answer to those interested in a web-radio solution

Action Message Format (AMF) is a compact binary format that is used to
ActionScript object graphs. Once serialized an AMF encoded object graph
to persist and retrieve the public state of an application across sessions or
endpoints to communicate through the exchange of strongly typed data.

And Java-Remoting BlazeDS Beta

BlazeDS is the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Adobe Flex and Adobe AIR applications for more responsive rich Internet application (RIA) experiences.

Previously available only as part of Adobe LiveCycle Data Services ES, Adobe is announcing its plans to contribute the proven BlazeDS technologies to the community under the LGPL v3. BlazeDS gives the rapidly growing Adobe developer community free access to the powerful remoting and messaging technologies developed by Adobe.

The source code will be available for download in early 2008.

In short: more AMF servers for free, other than RED5

Today someone in a comment warned me that I have some spam links in the footer visible only with javascripts disabled.

I’ve updated wordpress some days ago because I’ve noticed some spam links in my sidebar, but as it seems this wasn’t enough to fix the problem.

Luckily, I’m using subversion to manage wordpress updates, in this way I can see what happened to my wordpress:

? wp-includes/class-mail.php
M 6377 wp-includes/default-filters.php
M 6377 wp-includes/wp-db.php
M 6377 wp-includes/gettext.php
M 6377 wp-includes/pluggable.php
M 6377 xmlrpc.php
M 6377 index.php
M 6377 wp-admin/admin.php
M 6377 wp-admin/index.php


There was a new file class-mail.php and the others were modified.
Luckily nothing that a few svn revert commands couldn’t heal

If you want to check if you blog has the same “guest” links:

1. disable javascripts
2. look at your footer.

If so:

1. replace those files marked with M
2. delete class-mail.php

More info on this exploit: Phentermine attack
This episode is the proof of how useful is to install/update wordpress with subversion: Install wordpress with subversion

This uses the original Doom shareware wad file and gets all content from it at runtime.

See it here: Flash Doom game

What are continuations?

A continuation represent the state of execution of a function: all the local variables and the instruction pointer (the last line executed).
(Update: At least: there can be many kind of continuations. Other than the local variables, it's possible to store the state of the entire thread/process/stack)

What are them used for?

You can interrupt the execution of a function and resume it later.
This can be useful to create "generators": iterators made simple.

A generator looks like this:

The function next return the next element in the arr array every time is called.

When you call the function you resume the continuation, so the execution will resume from the yield.
If you want to implement an iterator like that without generators you'll have to explicitly unroll the for loop.

The resulting code will be surely less readabe.
Like:

This can get really worse for every non-trivial iterator (eg: tree traversal).

Another nice use of continuations is to generate cooperative threads.
They are different from standard threads because they can't be stopped, they should cooperatively stop.

For example you can do:

The process function return the control to the calling function every time it has to do an asynchronous operation.
Without continuations you'll have to do:

As you can see we have used closures in a Continuation Passing Style:
Every time you have to do an asynchronous operation, you'll have to pass a function (a callback) that will be called when the operation is done.

Without closures the code will look even worst, this is why recently there is a great buzz about closures in the java world.

But, what have in common continuations and threads?

A continuations-like style of programming (but without continuations) is possible only using threads.
However, threads are the heavier and most problematic way to handle the I/O waitings. (see: 10Kproblem)
You have not only to deal with concurrency problems with read/write variables, but you have to block an entire thread for every I/O operation.
A better way is to use asynchronous events, like in the last two example. But of the two, which one do you prefer?

If your answer is like mine, take a look to:

• Jetty servlet engine, it support a limited form of one shot continuations: the function is re-executed from the beginning, what is restored is only the HTTP connection state.
• RIFE continuations, it's a bytecode-level implementation in Java, these are real continuations
• NarrativeJS, a precompiler that create a simple form of continuations in Javascript: using the -> operator the execution can be resumed from that point.
• Update: Torsten Curdt suggest Javaflow, a continuation implementation that seems really interesting, he offers some tutorials on his blog too

Jetty scratched only the surface of what is possible with continuations, while with RIFE it's possible to develop highly concurrent servers using cooperative sessions instead of threads (some >10000 connections instead of 1000). See: Mina Java-NIO library, Perl POE, Mina-Mule.

A server that uses continuations, will allow the simple and linear programming style of blocking-synchronous operations while using non-blocking ones. With a huge increment in performance.

In the client side, the most interesting is NarrativeJs, that use an approach that can be adapted to every language:
it unroll loops and transform all local variables in object variables to generate his quasi-continuations.

became:

The code looks ugly but it is so to preserve line numbers.
With narrativeJs you can do complex animations in a simple, linear way:

or:

Really interesting now that Flash and Ajax are pushing asynchronous operations to the masses.
Will we say goodbye to events, and maybe to threads as we know now?

I've done a "droplet" that upload and resize pictures and folders with FTP.

Why?
Since I was looking for a simple and opensource "droplet" application, and I haven't found one.

The requisites was quite simple:

• upload files of some Mbs
• resize large pictures to speed upload
• SIMPLE: use drag&drop
• upload folders too

This is the result:

Download applet/droplet + sources

To use it:

1. Download the jar+html example
2. open sample.html
3. Drag image files and folders of pictures
4. Upload

In net\madarco\lightview\UploadApplet\FtpParameters.properties (in the jar, use winrar to open it) you can configure the ftp parameters. Beware that the user&pass would be accessible in the .jar, so don't deploy this applet in a public area.
In the next releases (if there will be) I could implement an Http upload or prompt the user for the password.

This applet is released as Public Domain, use it as you will. In the jar you'll find the source. Hope you'll enjoy it.

Know bugs:

Can upload only once
Can't run as standalone application
Save always as Jpg (but accept gif and bmp too :P) Ok, we can live with that
Those bugs are easy to fix, eventually I'll do that, depending on my laziness done!

If you are interested in how is done, continue reading:

How to do a ftp droplet and applet that resizes images

The best(lazy) way to achieve the upload of large files and folders is to use ftp. For this I've used org.apache.commons.net.ftp classes. They are simple and well documented.

To start, see the FtpUploader class.
It basically iterate the files and folders specified in the swing tree component and upload them through the doUploadFile member

doUploadFile upload files from a stream, in this way we can monitor the progress:

The resizeImage method of the JpgResizer class do what his name says:

For the drag&drop code see DropFilesHandler class, in the drop method you can find the code that get the file name dropped.

Simple, isn't it?

To run it as an applet, you'll have to sign it. This is a good guide.
In short:

The code is really quick&dirty, however, even if there are many things that can be improved, this can be used as a base to implement your own droplet.