bLOGical
Carpe Diem "Weblog reporting on Advanced Technologies, Grid-Computing, XML WebServices, Semantic Web and Java / Python development"
 
                                                                                                         
   Updated: 11/12/2003; 2:09:08 PM.            

>

Wednesday, October 01, 2003
> Web Services Reliable Messaging..
Web Services Reliable Messaging.. Prasad Yendluri, principal architect at webMethods, has written this good look at the issues surrounding reliable-messaging protocols. He begins with the objectives and explains why, in a multi-hop architecture such as will be typical for web services, we need protocols that operate at a level above the hop-to-hop transports. He then describes the prior art of RosettaNet, BizTalk, and ebXML.

The meat of the paper is a good and detailed presentation of WS-Reliability, of which webMethods is a co-sponsor to OASIS. Finally, the author explains the differences between that protocol and WS-Reliable Messaging proposed by IBM, Microsoft, and BEA. He says it's "a hurried response to the WS-Reliability specification...[one for which] the authors of the specification reserve all intellectual property rights...[and that it contains] dependencies on other proprietary specifications such as WS-Policy...Despite any potential merits and new concepts introduced by WS-Reliable Messaging, the specification is plagued by intellectual-property issues associated with the specification."

The paper contains valuable explanations and examples, but consider the source with regard to the politics. [Source: webservices.org] [Blogarithms]

> A Continuum of Services.
A Continuum of Services.. I've been thinking about this scale of service architectures:
  • Wrappers
  • URI-based GET/POST interfaces (e.g., REST)
  • SOAs
  • Orchestration
What are the properties that place these concepts on a continuum? For one, this is the sequence in which most IT shops are implementing web services. It also tracks the scales of tight-to-loose coupling and the availability of supporting technologies. [Doug Kaye: Web Services Strategies]
> Mobile/Photo/J2ME Blogging with PersonalBlog.
Mobile/Photo/J2ME Blogging with PersonalBlog.

Well I finished another chunck of mobile blogging functionality. I wasn't satisfied with merely posting from my mobile phone. My Sanyo 8100 has a built-on camera, and I want to include pictures taken from my phone in my mobile posts. However the Sanyo 8100's J2ME implementation doesn't allow a midlet to access any of the camera functions.

Since the camera can send pictures via email, I decided to explore the alternative of sending emails to my weblog. So I created a new email account just for my weblog. I added some new code to PersonalBlog for reading any emails in the the email account's inbox. I didn't want to waste to much time studying the java api for accessing emails, so I borrowed snippets of email processing code from Moblogger. (I hope you don't mind Russ.) Things were going well, but Sprint PCS threw me a curveball.

When a Sprint PCS subscriber sends a photo taken with a camera phone, the email doesn't include the photo in an email attachment. Instead you actually get a html email which contains an image tag that references an image stored on Sprint's website. So I needed to write some code that would parse the email to find the url of the image. I haven't had much experience doing this, but I figured it out.

Once I had the image URL, I wrote some more code using the java's ImageIO library that copied the JPG images from Sprint to my weblog. Since I wanted to preview the pictures from PersonalBlog Mobility on my mobile phone, I had to also write some code that would create PNG thumbnails because the J2ME implementation only can process PNG images. I think the CLDC only supports PNG images, but I'm not sure. Prior to this excercise I have never worked directly with the ImageIO library. This was another learning experience for me.

Next I added an additional service to PersonalBlog (using XML-RPC) that returns a list of images that were processed by PersonalBlog from emails sent by my phone.

Keep in mind that all the changes I've made so far have been to PersonalBlog (the Struts/Hibernate-based web application proudly built using JAVA). At this point no changes have been made to PersonalBlog Mobility (the J2ME midlet). With the changes to PersonalBlog complete, I was ready to embark on the changes to PersonalBlog Mobility.

PersonalBlog Mobility already had the ability to post entries to a PersonalBlog instance. I augmented it to retrieve the image list from PersonalBlog (via XML-RPC). When creating a new post from a mobile phone, I added a checkbox that indicates whether you want to include a picture taken with the phone. If so, you can scroll through the list of images. As you scroll up/down the list, the Mobility will show you a preview of the picture by retrieving the associated thumbnail (PNG) from PersonalBlog via HTTP. Once you select an image to be included in the mobile post, the original JPG image (not the PNG preview) is appended to the post.

Once you have added a title, selected one or more categories, selected a picture, and written the post, the post is submitted to PersonalBlog. Here is a weblog entry that was submitted from my Sanyo 8100.

This makes it very easy to include pictures taken with my camera-phone in my mobile posts. All I have to do is (1) Take picture with phone, (2) Send it to weblog email address, (3) Preview/Select the image using PersonalBlog Mobility. It literally takes less than a minute.

[java.blogs Day's Entries]
> Web Server Performance Myths.
Web Server Performance Myths.

Here is a recent semi-public paper on web server performance mentioned in a message to Tomcat developer mailing list. Download article.zip and read the PDF file inside the zip file. It has some interesting discussion about web server performance myths. Here is an choice excerpt:

[...] yahoo gets 1.5 billion pageviews a day. [...]

Yahoo uses 4,500 server to serve up 1.5 billion pageviews each day. If we divide that by the number of seconds in a day, we get 17,361 pageviews per second. Assuming the load is distributed evenly across the servers, each server handles 3-4 pageviews per second per system.

One of the key points the paper stresses is the performance/value offered by hardware XML accelerators for XML-happy web applications. There are other choice bits in the paper, so check it out before the authors take it offline.

[Don Park's Daily Habit]
> Web Services.
Integrating Services with XSLT. For all the magic that XML, SOAP, and WSDL offer in allowing businesses to interoperate, they do not solve the more traditional problems of integrating data models and message formats. This article shows how XSLT can be used to integrate data models across web services. Ausdrucken! [Der Schockwellenreiter]
> Web Services ii.
Web Services ii. "soup" What is Service-Oriented Architecture? Service-Oriented Architecture underpins most modern web services. It aims to achieve loose coupling between interacting software agents in order to preserve the benefits of reusability, extensibility and simplicity. Auch ausdrucken! [Der Schockwellenreiter]
> Bell Canada, Microsoft TV team up.
Bell Canada, Microsoft TV team up. The Canadian phone company plans to begin testing a new service that uses Microsoft technology to deliver video over telephone lines. [CNET News.com - Front Door]
> JBoss Resoruces.
Its not a complete list of JBoss resources yet, but the rough draft has some real gems, JBossResources .... [250 characters] [ShareMe Technologies-The Mobile Future]
> The WiSIP: new voice over WiFi phone.
The WiSIP: new voice over WiFi phone. Jeff Pulver's new company, pulverInnovations, has come out with a WiFi phone that can make VoIP phone calls over 802.11b. Right now the WiSIP is mainly meant to be used with Free World Dialup, Jeff's Voice over IP calling network for making free calls to other Free World Dialup users, so it's not rather limited in what you can do with it, but we chatted with Jeff yesterday, and he says they're working with Vonage to make a WiSIP phone that's compatible with Vonage's VoIP service. The big deal about that is that unlike Free World Dialup, users of Vonage's VoIP service can call any phone number anywhere and get a regular ten-digit phone number so they can receive calls just like they would on a landline. Combine that with a WiSIP, and suddenly you have a wireless phone that can make supercheap phone calls from anywhere you can get... [Gizmodo]

© Copyright 2003 Ed Pimentel.
 

October 2003
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Sep   Nov



Subscribe to "bLOGical" in Radio UserLand.

Click to see the XML version of this web page.
 

Click here to send an email to the editor of this weblog.