Neowin.net

SharpMT is an offline Blog writer that is designed for MovableType based systems. It allows a writer to write a new Blog entry on an offline computer and later upload it to an MT server with one click. SharpMT can also syncronize the list of categories and a cache of previously published posts that are already on the server, offering automated cross-entries links. The 1.1 release adds a new UI design for nested windows, a preview mode for existing drafts, upload imaging support, and a couple of bug fixes.

SharpMT 1.1 offers:

• Save drafts locally - save entries that you're working on to your local hard drive
  
• One button posting - send any of your drafts to the server with one button click
  
• Multiple categories per post - select more than one category for each draft published to the server
  
• Standard tag support - added bold, italics, underline, and URL tags via tool bar, menu, or keyboard
  
• Download existing posts - download a list of existing blog enties from your server and store it on your hard drive for linking and editing
  
• Sync-able links list - advanced download techniques will always minimize data request for new published posts
  
• Sync-able categories list - pull an updated category list from your server at anytime
  
• MT specific creation - use MT's extended fields, such as publishing status, categories, and excerpts
  
• Integrated Preview - built in Previewing allows you to view your drafts based on an HTML template
  
• Upload Images - upload any of your local images to anywhere within your blog
  
• Customizable toolbar images - change the look of SharpMT by changing two images
  
• Modern Looking UI - using the docking and floating window suppose of .NET for a modern interface

SharpMT is Donation-ware and requires the 1.1 version of the .NET Framework to run on a Windows-based PC.

Download: SharpMT 1.1
Screenshot: One | Two | Three
View: FAQ
News source: SharpMT Home Page

TCP breaks down large files into small packets of about 1500 bytes, each carrying the address of the sender and the recipient. The sending computer transmits a packet, waits for a signal from the recipient that acknowledges its safe arrival, and then sends the next packet.

If no receipt comes back, the sender transmits the same packet at half the speed of the previous one, and repeats the process, getting slower each time, until it succeeds.

This means that even minor glitches on the line can make a connection very sluggish. Because Fast TCP uses the same packet sizes as regular TCP, the hardware that carries messages around the net will still work. The difference is in software and hardware on the sending computer, which continually measures the time it takes for sent packets to arrive, and how long acknowledgements take to come back.

This reveals the delays on the line, giving early warnings of likely packet losses. The Fast TCP software uses this to predict the highest data rate the connection can support without losing data.

Since the packets are the same size as those used in TCP, none of the equipment along the internet itself will have to be modified, and no new hardware will be needed on computers receiving the data.

The first practical test of Fast TCP took place in November at a supercomputing conference. Researchers from Caltech, Stanford and CERN near Geneva in Switzerland, sent data 10,000 kilometres from Sunnyvale, California, to CERN at an average rate of 925 megabits per second. Ordinary TCP managed just 266 megabits per second on the same routes.

By ganging 10 Fast TCP systems together, the researchers have achieved transmission speeds of over 8.6 gigabits per second, which is more than 6000 times the capacity of ordinary broadband links.