Skip to content

Top Android annoyances.

HTC Desire / Android annoyances
  1. Keyboard drives me nuts with mistyping, even with swype
  2. Can’t accurately position cursor with touch
  3. Can’t swipe to delete email
  4. Can’t double touch to scroll web pages to the top
  5. SMS app doesn’t go back to main message list when I press back button
  6. SD card sometimes ‘mysteriously’ gets mounted as read only, meaning I can’t take photos/video without restarting phone.
  7. When out of battery, it starts to ‘shut down’, but never does, just has the ‘shutting down’ message forever…. until last gasp of battery
  8. Occasionally very slow to respond to touch events
  9. Runs out of disk space very quickly (all apps on internal storage), when it does, it will silently fail to check email until this error is corrected.
  10. Can’t search gmail inbox without a data connection.
  11. Uses *alot* of data, regularly using 1GB a data a month, when on iPhone used < 500MB
  12. Google sync goes batshit occasionally, gets in a endless sync mode (see point 10)
  13. Gmail inbox won’t sync changed to Gmail reliably.
  14. Active Sync with work Exchange is not reliable, often won’t check mail until app is killed and restarted.
  15. Zooming on web pages is sometimes problematic, zooming out when you pinch in
  16. Syncing music is a PITA, even with Doubletwist, which wins the award for being both slow and giving little feedback on sync progress.
  17. Won’t natively tether with my mac.
  18. Only tethers over cable, not bluetooth.
  19. Worse battery life than my iPhone 3G, esp overnight with data turned off, expect to use 1/3 battery.
  20. Screen hard to read in daylight
  21. No Froyo / 2.2 update for months after official release
  22. Music player doesn’t stop playing when you start watching a video (like on iPhone), sometimes not during calls.
  23. Proximity sensor is PITA when bluetooth is enabled, can’t ‘approach’ the phone from the left hand side without the screen blacking out.
  24. Limited access to accessories (power charges, cases etc).
  25. Doesn’t support a HTTP Proxy when on WiFi (won’t work at work then).
  26. Doesn’t support a fixed IP address when on WiFi (My home network has issues with DHCP working reliably)
  27. Updating apps sometimes fail, leaving invalid shortcuts on desktop.
  28. After installing an app (Locale), my Manage Applications area crashes every time you try to run it.
  29. Voice search is hilariously inaccurate

Good things

  1. Notifications system
  2. Chat is a viable application thanks to background tasks
  3. Phone still mostly usable when syncing
  4. Fast to use
  5. Some good quality applications
  6. Back button.

Posted in Tech.

By Steven
August 22, 2010

5 comments

Rimuhosting Support

Recently Rimuhosting remarked they were having a quiet day, so I raised an issue asking for a good weekend away suggestion near Wollongong (my home town).

I got this response within a few minutes…. :)

Heya

Thanks for your query regarding holiday locations. First of all, i would advise against going to such places as Wollongong. Its a dangerous place and contains a lot of Australians. Australians have a history of coming from primarily prisoners so we generally equate them with 3rd world type people.
According to the locals in wollongong they cant even make up their mind what the town name means ( http://en.wikipedia.org/wiki/Wollongong,_New_South_Wales )

Ideally you should take your holiday somewhere more like a tropical island, somewhere like New Zealand! Of course you would wait to make sure you enjoy the upper class people of the country so staying away from the main centers is a must, head for the smaller townships.
Since you are a computer geek, and would seek similar company I would suggest Cambridge is the place to be, i can arrange a tour guide complete with tour of the Rimuhosting offices and optional curry.
Included is free internet usage, plenty of coffee and free accommodation.

Let us know if you would be happy to arrange this and we will go ahead sorting that out right away.

Regards,
Liz Quilty
Rimuhosting.com

http://twitter.com/RHLiz

Posted in Tech.

By Steven
August 19, 2010

1 comment

Android on the Telstra Desire. First impressions.

I thought I’d just drop down my thoughts on moving from the iPhone 3G on Optus to a HTC Desire running Android on Telstra. These are rough thoughts, I hope to refine them over the next few days.

I’d like to note, this is my first impressions based on no googling to resolve any issues, or even reading the instructions. I’m going by ‘feel’.

Hardware

It’s feels like a substantial bit of quality kit and actually feels ‘soft’ to the touch, buttons are in the usual place, far more of them than the iPhone. And its fast, very fast (compared to the 3G)

Software

This is the first time i’ve spent with an Android phone, and this one is running HTC’s Sense UI. To be frank, I’m not sure what the difference is between Android ‘standard’ and what HTC Sense adds, but what I had read before purchasing had mentioned then HTC Sense was an improvement over the default Android behaviour. If that’s true – well, the gap between iPhone and Android is bigger than I thought.

Text entry

Entering text on the virtual keypad is pretty straightforward, I can’t say the buzzing on keystroke adds much, but the suggestion of multiple options for various words is an improvement over the iPhone, esp since one of the suggestions is what you actually typed, an absence of which on the iPhone was a petty annoyance of mine.

Sadly, the iPhones ability to position the cursor by touching the text and then using pressure and the magnifying glass to get it in the right spot is missing, instead you have to use the optical track pad to move the cursor around ‘old style’. Annoyingly my muscle memory makes me touch the text, resulting in a full screen context menu popping up.

Gestures

Some gestures from the iPhone carry over, pinching and zooming for instance, others however are lost, swiping to delete an email message or tapping the top of the browser window to fast scroll to the top. The later is an issue for me, long web pages must be ‘swiped and swiped’ to reach the top.

Performance

The phone is fast, very, very fast. Apps start almost instantly and web pages render almost as fast. I can’t fault it.

Telstra

Telstra brings its best asset to the party with the NextG network, its truly a revelation to me having come from Optus. I’ve made next to no calls on the phone, but the data is always available and always fast, staggeringly fast in some cases. YouTube loads without buffering, apps download and install, maps (and so on and so on). Being able to load the Bananaman intro from *normal* YouTube at a small cafe in Otford without a moments buffering…. well, unexpected after 2 years on the Optus network.

But Telstra adds its own annoyances, the BigPond team may have let you out of their walled garden, but they want you back, and so appear to add several apps to the phone, some of which duplicate what HTC have added – most of the apps turn out to be simply links back into the Telstra 3G web portal, and annoyingly, they don’t work when you are on WiFi – the Navigation app being a classic example of Telstra fail. Whilst its a ‘real app’, from Gamin, it only works when on NextG, and throws errors/crashes when started on WiFi. You also have to subscribe to a monthly plan to continue using it. Which is typical of the Telstra nickel and dime approach.

Applications

The phone comes with 3 mail applications, 2 navigation applications and many other duplicates, it seems Google have the Android standards, HTC throws in their ‘value add’, and Telstra rounds out the pack with its own. Many of them don’t seem to be able to be removed. The Android market contains Android version of my fav iPhone apps: Dropbox, Evernote, Twitter for Android, Foursquare. But its also seems to have its fair share of crap – alot of the ‘top sellers’ seems surprisingly amaturish. Oh, and you better have your credit card handy for any purchases.

Android

To be honest, I had higher expectations. The notification system and background apps really shine through – it’s a big improvement over the iPhone. But you can’t seem to quit applications – ever. Apparently Android manages this for you, but when you’ve got HTC Peep and Twitter for iPhone both running and telling you you have (The same) tweets, the flaw in this logic becomes apparent. Since I can’t seem to uninstall the HTC app, I’ve resorted to deleting my username/password from it. Hopefully it’ll get the idea and stop annoying me.

I pity non-technical users of the phone. The applications list under settings offers such installed items as “com.google.android….” and “Calendar” and “Calendar Storage”, or “Shared service provider”. It’s probably a bit too much of the internals exposed. And no, you can’t seem to uninstall the shovelware that HTC and Telstra have burdened you with.

Overall.

Its fast device that seems quite well made, the Telstra network seems, so far, to be much faster and more reliable than Optus but for me, the let down is Android which feels like iPhone OS on cocaine.

Let’s see if the true glory shines through over the next few days.

Posted in Tech.

By Steven
May 22, 2010

2 comments

How much Architecture do you need?

Recently a conversation came up on the Illegal Arguement converasation about ‘how much architecture is needed’, and I responded in a post on their mailing list.  This blog entry is an elaboration on that post.

In my opinion, that depends on your organisational context.

Some of the Architecture documentation I’ve constructed in my professional life has been in the kind of environment which is all about butt covering and decision justification, sadly the  communication of concepts to a team of developers is of secondary concern. 

In some cases, an external party would be included to do an Architecture Review on a design prior to approval.  Generally this was motivated by a visible failure in the past and there was a political concern that needed to be mitigated.  In short, it was an expensive form of box ticking. 

As an outcome, the reviewed documents needed to be  detailed and contain lots of redundant information and statements of what most would believe was the blatently obvious.  Further more, they needed to be structured around an industry best practise.  Not because it was the necessary thing, but because it was the expected thing.

By their nature these kind of documents were also completed well ahead of software construction, usually at business case stage and with technologies and frameworks picked like you might select a breakfast cereal (From
reading ‘the back of the box’).   A depressing way of doing things, but unavoidable given time and circumstance.

So whats the answer?

Personally, I feel its all  proportional to how much contact you have with the implementers of the solution and the strength of that relationship. In the environment I’m referring to above, I was  distant from them, in fact, on some of the projects, I wasn’t involved in delivery at all. Just the intial documents and pre-project meetings.

If thats your situation then there is no substitute for detail.  You needed to be explicit and obvious as the contractor who turned up yesterday is likely going implement the project ‘their way’ and it seems, people can come up with no end of variation from what rational thought might expect.

Further more if you are in a hostile environment, full of politics  and a low acceptance for any perceived failure (i.e. an ‘Enterprise’) then you are in for a hard time and you better get used to TOGAF, Zachmann, UML and your favorite design patterns book.

But, if you are directly involved in the delivery and a good relationship with the implementors, then I believe the required documentation should be  ‘not much’, you might even suffice maybe a list of bullet points and a few high level diagrams and suppliment it a constant stream of guiding conversations during the delivery process.

Posted in Tech.

By Steven
November 5, 2009

4 comments

XML – its not bad, it’s just used that way.

It’s pretty popular these days to kick XML, all the cool kids are doing it and they don’t seem to discriminate between its ‘good’ purposes and ‘bad’ uses.

The general comment seems to be: "XML is bad m’kay?"

Well, I disagree.

Sure, its a crappy programming language, a verbose wire protocol, its got a stack of super complicated standards and it’s been perverted into doing things you only find in the darker parts of the net, but it’s pretty good at one thing: Representing structured documents.

You know, what it actually was designed for.

So if you want to store (and/or exchange) Invoices, Insurance Policies, Application Forms, basically anything where structure is essential but variation inherent – XML is going to be your best friend.

But, its not all smooth sailing and over the  years of doing Business to Business XML based messaging across the Retail, Supply Chain, Transport and Insurance industries I’ve learned a few things:

Things not to worry about

Put concerns about performance and tooling to one side – performance isn’t an issue (most of the time) and no matter what you choose, all the tooling still sucks (sadly).  Learn to work with it :)

Things you should worry about

Don’t neglect your information design

Too often tools like XML Spy give people the impression that Schema design is a task that can be undertaken without to much thought.  (And in some cases, that can be true). 

But its not true for any document of any complexity, and just as you shouldn’t let random developers make uncontrolled additions to your domain model or database schema, you must protect your schemas with governance and review processes. 

If you can get a single person to be your "Schema Lord", do it.

Version control  your schema from the get go

You haven’t got it right and it will have to change.  Count it in from the beginning

Personally, I like the month/year style of dating the XSD files (myschema_092009.xsd).  And remember, you only need to change versions if its a breaking change.

All industry ‘standards’ suck

In my world, suck is defined as designed by committee.  As such they will be large, complicated and likely to be  so abstract they do not relate to your problem. 

Tooling often chokes on them as well, with all those imports and custom types, you often will hit breakages in your tooling.  Don’t trust it until you see it working yourself.

Further more, with the standards being so big their is a very strong chance that all parties will not have the same implementation of the ‘standard. 

Approach adoption of industry ‘standards’ with a pinch of salt and box of asprin – and be ready to cater for differences between implementations with any of your trading partners.

XML schema validation is only the beginning of your validation requirements

XML schema validation only validates a limited number of things, its not covering all of your problems.  Further more, most schema validation feedback is total garbage – you can’t show it to an end user, and you likely can’t even send it to a technical party. Keep this in mind.

You might need to deal with stuff that doesn’t validate

Got that fancy schema? Lots of mandatory elements because you want to be super awesome? Great.  I need to save the document as ‘draft’ – its a form that the user hasn’t finished filling in yet.

Ah, that tooling you’ve got where the first thing it does is validate the schema, yeah, it breaks now….

The people you deal with, might not ‘get it’.

There are a lot of people out there for whom XML is just a bunch of <  and > signs and nothing else.  CDATA? Validation?  Attributes?  Root elements?  Encoding? meh, its not important. 

So before you design your super format, check that the other party knows the basics and isn’t just treating XML asa  CSV format with lots of extra crud in it.

Sadly, your righteous indignation over their inability to conform to "the right way" may be morally correct, but it tends not to convince others, especially if they are paying the bills.

Conclusion

This is all pretty off the cuff stuff on my part, if you feel the need to have me elaborate, leave a comment :)

Posted in Software Development, Tech.

By Steven
October 29, 2009

1 comment

Personal Ethics

I received a document today from a colleague relating to a project we’re undertaking over the next few months.

The document had been prepared by my predecessor, somebody I haven’t met and have only heard about second hand.

I opened the document and my first impression was it was pretty robust and detailed piece of work.  It was quite well executed and full of some very specific advice about deploying SharePoint; particularly in a virtualized environment.

However, the more I read the more I noticed it’s unusual tone.   It seem a little to effusive and upbeat and its choice of tense in a few locations seemed to jar with the overall nature of the document.

It also contained a significant number of disclaimers, more than I’d ever seen in an internal document, and certainly more than I would expect given the nature of the organisation I’m currently working with.

So I decided to extract a few sentences and run them through Google.

And what did I find….

Of the eleven or so pages in the document, I’d say around 6 pages, the bulk of the text, were lifted directly, and without modification, from Microsoft documents about SharePoint.

No attribution, no references, no footnotes.  All of it claimed as original work.

In my opinion, a clear case of plagiarism.

Am I surprised?  Not entirely, I’ve been around long enough to see and hear about some pretty odd behaviors by people.

But it still leaves me incredulous that someone would risk their job and the professional reputation in such away.

Was it lazyness?  Was it a cover for lack of knowledge?  Was it lack of time?  Lack of motivation?

I’ll never know. 

But on the plus side, I’ve discovered some useful Microsoft documents about SharePoint :)

Posted in Software Development, Tech, Thoughts.

By Steven
October 28, 2009

3 comments

MOSS 2007 ECS (Excel Calculation Services) and Java (JAX-WS)

What the??

For those unfamiliar, the Enterprise Edition of Microsoft Office Sharepoint Server (MOSS) has an embedded MS-Excel engine which allows you to host Excel Spreadsheets on MOSS and have it be a hosted calculation engine, using an Excel Spreadsheet as its driving logic.  Further more, this excel spreadsheet can be exposed to the network over a SOAP based web service.

This permits you to access business logic stored within Excel from a traditional Java based web application.  An important concept if you are working with legacy formula’s or have a relatively low value problem that doesn’t wish to incur the cost of duplicating business logic in Java.

(Of course, this sidesteps the considerable cost (in some cases) of MOSS.  Best you check with your organisations MS agreement to see what it’s going to cost).

There are an number of ingredients in the process.

  1. You’ll need Sharepoint setup and configured
  2. You’ll need to configure up Excel Calculation Services on sharepoint
  3. You’ll need to clean up your spreadsheet to make it ECS compatible
  4. You’ll need to construct a Java client for talking to the Spreadsheet.

Getting Sharepoint running.

For my work, I took evaluation copies of

  • VMWare
  • MOSS 2007 Enterprise CAL  (See this product comparison spreadsheet and the Business intelligence tab within it).
  • MS Windows Server 2008

And I followed the instructions located here:

http://blogs.msdn.com/andreww/archive/2009/04/21/excel-services-setup-and-getting-started.aspx

The only additional rule to make the system work from outside was a change to the Windows Firewall to permit incoming TCP connections to the port that the Sharepoint website gets created on.

Cleaning up the Excel Spreadsheet

Excel Calculation Services is not compatible with all the features that are in MS Excel spreadsheets, specifically

  • Sheet protection
  • Data Validation
  • Comments
  • Shapes (Images, arrows, text boxes)
  • VBA (Macros)

You need to clean up the spreadsheet prior to loading it, and verify that your cleaning has been successful by “Viewing the file in Web Browser”.

To clean up the spreadsheet, you need to

  1. Unprotect all worksheets in the spreadsheet.
  2. Add this macro to the file, and run it to clean up comments and shapes
  3. Select all cells in any worksheet with data validation (drop boxes!) and delete the data validation.
  4. Save as a normal excel Spreadsheet (not the Macro enabled version) this cleans up the VBA you used to delete the other objects.

To publish the spreadsheet, select that stupid microsoft circle, then select ‘Publish’ and ‘Excel Web Services’ then pick the server details.

After it is published, it should open a web browser in web view, If it is successfully rendered in HTML, then it is ready for access over the web service.

The Java Client

My test client were created using using Netbeans 6.7 and its JAX-WS support, basically it consists of

  1. Consuming the WSDL for the Excel Data Services within netbeans (background information here and MS reference info here) and generating code
  2. Modifying your client to use the appropriate NTLM authentication details.

Inserting the calls to each web service  (right click in the main method, and select “Insert code” then “Call webservices operation” and then pick your call.

The basic steps you need to follow are:

  1. Open the workbook and obtain a session ID
  2. Add 1 to n values to either numbered cells (setCellA), or named cells (setCellA1) OR more efficiently, call setRangeA1 and muck around with Arrays.
  3. Call calculate on the worksheet
  4. Close the worksheet.

And that’s it!

Here is some sample code

Below is the minimal case using ranges.


public static void main(String[] args) {
MyAuthenticator myAuth = new MyAuthenticator("dontfreakout\\administrator", "mr31#UE");
Authenticator.setDefault(myAuth);

String sessionId = "";

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String workbookPath = "http://win-0v6f2x2aun4:32089/sites/phoenix2/Rating%20engine/Phoenix%20Strata.xlsx";
java.lang.String uiCultureName = "";
java.lang.String dataCultureName = "";
javax.xml.ws.Holder<java.lang.String> openWorkbookResult = new javax.xml.ws.Holder<java.lang.String>();
javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus> status = new javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus>();
port.openWorkbook(workbookPath, uiCultureName, dataCultureName, openWorkbookResult, status);

sessionId = openWorkbookResult.value;
} catch (Exception ex) {
// TODO handle custom exceptions here
}

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String sheetName = "Phoenix";
java.lang.String rangeName = "INPUTS";
com.microsoft.schemas.office.excel.server.webservices.ArrayOfAnyType rangeValues = new com.microsoft.schemas.office.excel.server.webservices.ArrayOfAnyType();

/*  Now we set all the values in the range by adding them to the list, basically its a top down table.
*/
rangeValues.getAnyType().add("01/01/2009");
rangeValues.getAnyType().add("31/12/2009");
rangeValues.getAnyType().add("My Policy Number");
rangeValues.getAnyType().add("Strata number");
rangeValues.getAnyType().add("3000");
rangeValues.getAnyType().add("20000000");
rangeValues.getAnyType().add("Non Brick");
rangeValues.getAnyType().add("20");
rangeValues.getAnyType().add("2");
rangeValues.getAnyType().add("YES");
rangeValues.getAnyType().add("15000000");
rangeValues.getAnyType().add("0");
rangeValues.getAnyType().add("2000");
rangeValues.getAnyType().add("1");
rangeValues.getAnyType().add("2");
rangeValues.getAnyType().add("10000000");
rangeValues.getAnyType().add("2");
rangeValues.getAnyType().add("4000000");
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.setRangeA1(sessionId, sheetName, rangeName, rangeValues);
System.out.println("Result = " + result);
} catch (Exception ex) {
// TODO handle custom exceptions here
}

/*
* You also now need to explicitly call calc on the spreadsheet, so your updates now have an outcome.
*/
try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
com.microsoft.schemas.office.excel.server.webservices.CalculateType calculateType = null;
// TODO process result here
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.calculateWorkbook(sessionId, calculateType);
System.out.println("Result = " + result);
} catch (Exception ex) {
// TODO handle custom exceptions here
}

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String sheetName = "Phoenix";
java.lang.String rangeName = "ALL_TOTALS";
boolean formatted = false;
javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfAnyType> getRangeA1Result = new javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfAnyType>();
javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus> status = new javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus>();
port.getRangeA1(sessionId, sheetName, rangeName, formatted, getRangeA1Result, status);

/*  It gets funky here as we are handling of a two dimensional array response (as the totals result is a 2d grid)
*
*  It's top to down, left to right
*/

Iterator i = getRangeA1Result.value.getAnyType().iterator();
while (i.hasNext()) {

Iterator j = ((ArrayOfAnyType)i.next()).getAnyType().iterator();
while (j.hasNext()) {
System.out.println(j.next());
}
}
System.out.println("Finished");
} catch (Exception ex) {
ex.printStackTrace();
}

}

Below is the minimal case setting cells one by one, you’ll need the supporting libraries of course and the code generated, best to open the project.


/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package sharepointtest1;

import java.net.Authenticator;

/**
*
* @author sherod
*/
public class Main {

/**
* @param args the command line arguments
*/
public static void main(String[] args) {

/*
* This is a custom authenticator to override what java does on your machine by default.
* What it does, by default, is pass the authenticated windows user who is running the program
* when it is challenged by sharepoint for NTLM credentials.
*
* Adding a custom authenticator here allows you to inject different credentials, to cheat, I've justed the
* administrator details for the Virtual machine, they have admin rights to Sharepoint.
*/
MyAuthenticator myAuth = new MyAuthenticator("dontfreakout\\administrator", "password");
Authenticator.setDefault(myAuth);

String sessionId = "";

/* Open the workbook.  Note the path to the location of the workbook inside sharepoint
* also note the way we get back the sessionId, you'll need this to maintain state for the subsequent webservices calls
*/

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String workbookPath = "http://win-0v6f2x2aun4:32089/sites/testsite/Test%20library/Simple%20spreadsheet.xlsb";
java.lang.String uiCultureName = "";
java.lang.String dataCultureName = "";
javax.xml.ws.Holder<java.lang.String> openWorkbookResult = new javax.xml.ws.Holder<java.lang.String>();
javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus> status = new javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus>();
port.openWorkbook(workbookPath, uiCultureName, dataCultureName, openWorkbookResult, status);

sessionId = openWorkbookResult.value;
} catch (Exception ex) {
// TODO handle custom exceptions here
}

System.out.println("Session ID?:" + sessionId);

/* Now we make the setCellA1 call to place values into the spreadsheet.
* Note this is using the named ranges approach, note the name of the Sheet1 and the range.
*
* You could also use setCell, and use x/y coordinates.
*/

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String sheetName = "Sheet1";
java.lang.String rangeName = "Sales";
java.lang.Object cellValue = new Integer(1000000);
// TODO process result here
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.setCellA1(sessionId, sheetName, rangeName, cellValue);
System.out.println("Result = "+result);
} catch (Exception ex) {
// TODO handle custom exceptions here
}

try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String sheetName = "Sheet1";
java.lang.String rangeName = "Costs";
java.lang.Object cellValue = new Integer(860000);
// TODO process result here
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.setCellA1(sessionId, sheetName, rangeName, cellValue);
System.out.println("Result = "+result);
} catch (Exception ex) {
// TODO handle custom exceptions here
}

/*
* You also now need to explicitly call calc on the spreadsheet, so your updates now have an outcome.
*/
try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
com.microsoft.schemas.office.excel.server.webservices.CalculateType calculateType = null;
// TODO process result here
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.calculateWorkbook(sessionId, calculateType);
System.out.println("Result = "+result);
} catch (Exception ex) {
// TODO handle custom exceptions here
}

/*
* Now read the result, from a named cell.  In this case, we use its excel generated name of C4 (not like the cell settings
*/
try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
java.lang.String sheetName = "Sheet1";
java.lang.String rangeName = "C4";
boolean formatted = false;
javax.xml.ws.Holder<java.lang.Object> getCellA1Result = new javax.xml.ws.Holder<java.lang.Object>();
javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus> status = new javax.xml.ws.Holder<com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus>();
port.getCellA1(sessionId, sheetName, rangeName, formatted, getCellA1Result, status);

System.out.println("\n******\nResult:" + getCellA1Result.value + "\n********");
} catch (Exception ex) {
// TODO handle custom exceptions here
}

/*
* And Close
*/
try { // Call Web Service Operation
com.microsoft.schemas.office.excel.server.webservices.ExcelService service = new com.microsoft.schemas.office.excel.server.webservices.ExcelService();
com.microsoft.schemas.office.excel.server.webservices.ExcelServiceSoap port = service.getExcelServiceSoap12();
// TODO initialize WS operation arguments here
// TODO process result here
com.microsoft.schemas.office.excel.server.webservices.ArrayOfStatus result = port.closeWorkbook(sessionId);
System.out.println("Closed workbook");
} catch (Exception ex) {
// TODO handle custom exceptions here
}

}
}

And here is the WSDL that MOSS generates (you should use the one your site has generated, not this one!)

<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 

xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" 

xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" 

xmlns:tns="http://schemas.microsoft.com/office/excel/server/webservices" 

xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" 

xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" 

targetNamespace="http://schemas.microsoft.com/office/excel/server/webservices" 

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <wsdl:types>
 <s:schema elementFormDefault="qualified" 

targetNamespace="http://schemas.microsoft.com/office/excel/server/webservices">
 <s:element name="GetApiVersion">
 <s:complexType />
 </s:element>
 <s:element name="GetApiVersionResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetApiVersionResult" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:complexType name="ArrayOfStatus">
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="unbounded" name="Status" nillable="true" type="tns:Status" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="Status">
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="Name" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="Severity" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="Message" type="s:string" />
 </s:sequence>
 </s:complexType>
 <s:element name="OpenWorkbook">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="workbookPath" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="uiCultureName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="dataCultureName" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="OpenWorkbookResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="OpenWorkbookResult" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CloseWorkbook">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CloseWorkbookResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="Refresh">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="connectionName" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="RefreshResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="Calculate">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeCoordinates" type="tns:RangeCoordinates" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:complexType name="RangeCoordinates">
 <s:sequence>
 <s:element minOccurs="1" maxOccurs="1" name="Row" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="Column" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="Height" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="Width" type="s:int" />
 </s:sequence>
 </s:complexType>
 <s:element name="CalculateResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CalculateA1">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeName" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CalculateA1Response">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetRange">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeCoordinates" type="tns:RangeCoordinates" />
 <s:element minOccurs="1" maxOccurs="1" name="formatted" type="s:boolean" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetRangeResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetRangeResult" type="tns:ArrayOfAnyType" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:complexType name="ArrayOfAnyType">
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="unbounded" name="anyType" nillable="true" />
 </s:sequence>
 </s:complexType>
 <s:complexType name="TypeExporter">
 <s:sequence>
 <s:element minOccurs="1" maxOccurs="1" name="CellError" type="tns:CellError" />
 </s:sequence>
 </s:complexType>
 <s:simpleType name="CellError">
 <s:restriction base="s:string">
 <s:enumeration value="Div0" />
 <s:enumeration value="NA" />
 <s:enumeration value="Name" />
 <s:enumeration value="Null" />
 <s:enumeration value="Num" />
 <s:enumeration value="Ref" />
 <s:enumeration value="Value" />
 </s:restriction>
 </s:simpleType>
 <s:element name="GetRangeA1">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeName" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="formatted" type="s:boolean" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetRangeA1Response">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetRangeA1Result" type="tns:ArrayOfAnyType" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetCell">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="row" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="column" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="formatted" type="s:boolean" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetCellResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetCellResult" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetCellA1">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeName" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="formatted" type="s:boolean" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetCellA1Response">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetCellA1Result" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetRange">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeCoordinates" type="tns:RangeCoordinates" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeValues" type="tns:ArrayOfAnyType" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetRangeResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetRangeA1">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeValues" type="tns:ArrayOfAnyType" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetRangeA1Response">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetCell">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="row" type="s:int" />
 <s:element minOccurs="1" maxOccurs="1" name="column" type="s:int" />
 <s:element minOccurs="0" maxOccurs="1" name="cellValue" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetCellResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetCellA1">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="sheetName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="rangeName" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="cellValue" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="SetCellA1Response">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CalculateWorkbook">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="calculateType" type="tns:CalculateType" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:simpleType name="CalculateType">
 <s:restriction base="s:string">
 <s:enumeration value="Recalculate" />
 <s:enumeration value="CalculateFull" />
 </s:restriction>
 </s:simpleType>
 <s:element name="CalculateWorkbookResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetSessionInformation">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetSessionInformationResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="serverVersion" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="uiCultureNameUsed" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="dataCultureNameUsed" type="s:string" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CancelRequest">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="CancelRequestResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:element name="GetWorkbook">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="sessionId" type="s:string" />
 <s:element minOccurs="1" maxOccurs="1" name="workbookType" type="tns:WorkbookType" />
 </s:sequence>
 </s:complexType>
 </s:element>
 <s:simpleType name="WorkbookType">
 <s:restriction base="s:string">
 <s:enumeration value="FullWorkbook" />
 <s:enumeration value="FullSnapshot" />
 <s:enumeration value="PublishedItemsSnapshot" />
 </s:restriction>
 </s:simpleType>
 <s:element name="GetWorkbookResponse">
 <s:complexType>
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="1" name="GetWorkbookResult" type="s:base64Binary" />
 <s:element minOccurs="0" maxOccurs="1" name="status" type="tns:ArrayOfStatus" />
 </s:sequence>
 </s:complexType>
 </s:element>
 </s:schema>
 </wsdl:types>
 <wsdl:message name="GetApiVersionSoapIn">
 <wsdl:part name="parameters" element="tns:GetApiVersion" />
 </wsdl:message>
 <wsdl:message name="GetApiVersionSoapOut">
 <wsdl:part name="parameters" element="tns:GetApiVersionResponse" />
 </wsdl:message>
 <wsdl:message name="OpenWorkbookSoapIn">
 <wsdl:part name="parameters" element="tns:OpenWorkbook" />
 </wsdl:message>
 <wsdl:message name="OpenWorkbookSoapOut">
 <wsdl:part name="parameters" element="tns:OpenWorkbookResponse" />
 </wsdl:message>
 <wsdl:message name="CloseWorkbookSoapIn">
 <wsdl:part name="parameters" element="tns:CloseWorkbook" />
 </wsdl:message>
 <wsdl:message name="CloseWorkbookSoapOut">
 <wsdl:part name="parameters" element="tns:CloseWorkbookResponse" />
 </wsdl:message>
 <wsdl:message name="RefreshSoapIn">
 <wsdl:part name="parameters" element="tns:Refresh" />
 </wsdl:message>
 <wsdl:message name="RefreshSoapOut">
 <wsdl:part name="parameters" element="tns:RefreshResponse" />
 </wsdl:message>
 <wsdl:message name="CalculateSoapIn">
 <wsdl:part name="parameters" element="tns:Calculate" />
 </wsdl:message>
 <wsdl:message name="CalculateSoapOut">
 <wsdl:part name="parameters" element="tns:CalculateResponse" />
 </wsdl:message>
 <wsdl:message name="CalculateA1SoapIn">
 <wsdl:part name="parameters" element="tns:CalculateA1" />
 </wsdl:message>
 <wsdl:message name="CalculateA1SoapOut">
 <wsdl:part name="parameters" element="tns:CalculateA1Response" />
 </wsdl:message>
 <wsdl:message name="GetRangeSoapIn">
 <wsdl:part name="parameters" element="tns:GetRange" />
 </wsdl:message>
 <wsdl:message name="GetRangeSoapOut">
 <wsdl:part name="parameters" element="tns:GetRangeResponse" />
 </wsdl:message>
 <wsdl:message name="GetRangeA1SoapIn">
 <wsdl:part name="parameters" element="tns:GetRangeA1" />
 </wsdl:message>
 <wsdl:message name="GetRangeA1SoapOut">
 <wsdl:part name="parameters" element="tns:GetRangeA1Response" />
 </wsdl:message>
 <wsdl:message name="GetCellSoapIn">
 <wsdl:part name="parameters" element="tns:GetCell" />
 </wsdl:message>
 <wsdl:message name="GetCellSoapOut">
 <wsdl:part name="parameters" element="tns:GetCellResponse" />
 </wsdl:message>
 <wsdl:message name="GetCellA1SoapIn">
 <wsdl:part name="parameters" element="tns:GetCellA1" />
 </wsdl:message>
 <wsdl:message name="GetCellA1SoapOut">
 <wsdl:part name="parameters" element="tns:GetCellA1Response" />
 </wsdl:message>
 <wsdl:message name="SetRangeSoapIn">
 <wsdl:part name="parameters" element="tns:SetRange" />
 </wsdl:message>
 <wsdl:message name="SetRangeSoapOut">
 <wsdl:part name="parameters" element="tns:SetRangeResponse" />
 </wsdl:message>
 <wsdl:message name="SetRangeA1SoapIn">
 <wsdl:part name="parameters" element="tns:SetRangeA1" />
 </wsdl:message>
 <wsdl:message name="SetRangeA1SoapOut">
 <wsdl:part name="parameters" element="tns:SetRangeA1Response" />
 </wsdl:message>
 <wsdl:message name="SetCellSoapIn">
 <wsdl:part name="parameters" element="tns:SetCell" />
 </wsdl:message>
 <wsdl:message name="SetCellSoapOut">
 <wsdl:part name="parameters" element="tns:SetCellResponse" />
 </wsdl:message>
 <wsdl:message name="SetCellA1SoapIn">
 <wsdl:part name="parameters" element="tns:SetCellA1" />
 </wsdl:message>
 <wsdl:message name="SetCellA1SoapOut">
 <wsdl:part name="parameters" element="tns:SetCellA1Response" />
 </wsdl:message>
 <wsdl:message name="CalculateWorkbookSoapIn">
 <wsdl:part name="parameters" element="tns:CalculateWorkbook" />
 </wsdl:message>
 <wsdl:message name="CalculateWorkbookSoapOut">
 <wsdl:part name="parameters" element="tns:CalculateWorkbookResponse" />
 </wsdl:message>
 <wsdl:message name="GetSessionInformationSoapIn">
 <wsdl:part name="parameters" element="tns:GetSessionInformation" />
 </wsdl:message>
 <wsdl:message name="GetSessionInformationSoapOut">
 <wsdl:part name="parameters" element="tns:GetSessionInformationResponse" />
 </wsdl:message>
 <wsdl:message name="CancelRequestSoapIn">
 <wsdl:part name="parameters" element="tns:CancelRequest" />
 </wsdl:message>
 <wsdl:message name="CancelRequestSoapOut">
 <wsdl:part name="parameters" element="tns:CancelRequestResponse" />
 </wsdl:message>
 <wsdl:message name="GetWorkbookSoapIn">
 <wsdl:part name="parameters" element="tns:GetWorkbook" />
 </wsdl:message>
 <wsdl:message name="GetWorkbookSoapOut">
 <wsdl:part name="parameters" element="tns:GetWorkbookResponse" />
 </wsdl:message>
 <wsdl:portType name="ExcelServiceSoap">
 <wsdl:operation name="GetApiVersion">
 <wsdl:input message="tns:GetApiVersionSoapIn" />
 <wsdl:output message="tns:GetApiVersionSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="OpenWorkbook">
 <wsdl:input message="tns:OpenWorkbookSoapIn" />
 <wsdl:output message="tns:OpenWorkbookSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="CloseWorkbook">
 <wsdl:input message="tns:CloseWorkbookSoapIn" />
 <wsdl:output message="tns:CloseWorkbookSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="Refresh">
 <wsdl:input message="tns:RefreshSoapIn" />
 <wsdl:output message="tns:RefreshSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="Calculate">
 <wsdl:input message="tns:CalculateSoapIn" />
 <wsdl:output message="tns:CalculateSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="CalculateA1">
 <wsdl:input message="tns:CalculateA1SoapIn" />
 <wsdl:output message="tns:CalculateA1SoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetRange">
 <wsdl:input message="tns:GetRangeSoapIn" />
 <wsdl:output message="tns:GetRangeSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetRangeA1">
 <wsdl:input message="tns:GetRangeA1SoapIn" />
 <wsdl:output message="tns:GetRangeA1SoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetCell">
 <wsdl:input message="tns:GetCellSoapIn" />
 <wsdl:output message="tns:GetCellSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetCellA1">
 <wsdl:input message="tns:GetCellA1SoapIn" />
 <wsdl:output message="tns:GetCellA1SoapOut" />
 </wsdl:operation>
 <wsdl:operation name="SetRange">
 <wsdl:input message="tns:SetRangeSoapIn" />
 <wsdl:output message="tns:SetRangeSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="SetRangeA1">
 <wsdl:input message="tns:SetRangeA1SoapIn" />
 <wsdl:output message="tns:SetRangeA1SoapOut" />
 </wsdl:operation>
 <wsdl:operation name="SetCell">
 <wsdl:input message="tns:SetCellSoapIn" />
 <wsdl:output message="tns:SetCellSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="SetCellA1">
 <wsdl:input message="tns:SetCellA1SoapIn" />
 <wsdl:output message="tns:SetCellA1SoapOut" />
 </wsdl:operation>
 <wsdl:operation name="CalculateWorkbook">
 <wsdl:input message="tns:CalculateWorkbookSoapIn" />
 <wsdl:output message="tns:CalculateWorkbookSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetSessionInformation">
 <wsdl:input message="tns:GetSessionInformationSoapIn" />
 <wsdl:output message="tns:GetSessionInformationSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="CancelRequest">
 <wsdl:input message="tns:CancelRequestSoapIn" />
 <wsdl:output message="tns:CancelRequestSoapOut" />
 </wsdl:operation>
 <wsdl:operation name="GetWorkbook">
 <wsdl:input message="tns:GetWorkbookSoapIn" />
 <wsdl:output message="tns:GetWorkbookSoapOut" />
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="ExcelServiceSoap" type="tns:ExcelServiceSoap">
 <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
 <wsdl:operation name="GetApiVersion">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetApiVersion" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="OpenWorkbook">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/OpenWorkbook" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CloseWorkbook">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CloseWorkbook" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="Refresh">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/Refresh" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="Calculate">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/Calculate" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CalculateA1">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CalculateA1" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetRange">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetRange" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetRangeA1">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetRangeA1" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetCell">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetCell" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetCellA1">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetCellA1" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetRange">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetRange" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetRangeA1">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetRangeA1" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetCell">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetCell" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetCellA1">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetCellA1" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CalculateWorkbook">
 <soap:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CalculateWorkbook" style="document" 

/>
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetSessionInformation">
 <soap:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetSessionInformation" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CancelRequest">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CancelRequest" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetWorkbook">
 <soap:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetWorkbook" 

style="document" />
 <wsdl:input>
 <soap:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:binding name="ExcelServiceSoap12" type="tns:ExcelServiceSoap">
 <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
 <wsdl:operation name="GetApiVersion">
 <soap12:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetApiVersion" style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="OpenWorkbook">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/OpenWorkbook" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CloseWorkbook">
 <soap12:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CloseWorkbook" style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="Refresh">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/Refresh" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="Calculate">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/Calculate" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CalculateA1">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CalculateA1" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetRange">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetRange" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetRangeA1">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetRangeA1" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetCell">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetCell" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetCellA1">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetCellA1" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetRange">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetRange" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetRangeA1">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetRangeA1" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetCell">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetCell" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="SetCellA1">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/SetCellA1" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CalculateWorkbook">
 <soap12:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CalculateWorkbook" style="document" 

/>
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetSessionInformation">
 <soap12:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetSessionInformation" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="CancelRequest">
 <soap12:operation 

soapAction="http://schemas.microsoft.com/office/excel/server/webservices/CancelRequest" style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 <wsdl:operation name="GetWorkbook">
 <soap12:operation soapAction="http://schemas.microsoft.com/office/excel/server/webservices/GetWorkbook" 

style="document" />
 <wsdl:input>
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="ExcelService">
 <wsdl:port name="ExcelServiceSoap" binding="tns:ExcelServiceSoap">
 <soap:address location="http://win-0v6f2x2aun4:32089/sites/testsite/_vti_bin/ExcelService.asmx" />
 </wsdl:port>
 <wsdl:port name="ExcelServiceSoap12" binding="tns:ExcelServiceSoap12">
 <soap12:address location="http://win-0v6f2x2aun4:32089/sites/testsite/_vti_bin/ExcelService.asmx" />
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>

Posted in Tech.

By Steven
August 5, 2009

No comments

The National Broadband Network – my thoughts (#nbn)

The Australian Federal Government has announced a $43 billion, 8 year plan to roll out fiber optic broadband to 90% of Australians, offering speeds up to 100Mbps to the homes and business of those within reach of the roll out.

I think by any measure this is a significant event and one that will benefit Australia’s economy, it’s environment and social fabric.  The plan however, has its detractors, and to my mind, some of the criticism borders on the bizzare.

Here are some of the arguments I’ve heard in the past 48 hours:

1. Australia is too large for it to be economically viable.

Australia is undoubtably a vast country, but when you consider we seem to have been successful in rolling out and sustaining roads, plumbing, power cables and copper phone networks over similar distances one wonders why there is a perceived difference with a few centimeters width of fibre optic cable..  I view fiber to the home as pretty much the same kind of basic utility – and compared to running railway track cross 2000KM of rivers, desert and mountains it should be significantly less impact, cost and effort.

2. It will be too expensive for people to use.

Prices quoted are in the order of $80/$90 per month – and yes, for many people, that’s alot of money, but I think it needs to be put into context, most users of home telephony pay similar amounts for line rental and very basic ADSL (and this network would supplant both).  Additionally, a mere 10 years ago I paid up to $5 an hour for internet access!  Finally, $80 a month is approximate to the charges levied for NextG wireless net from Telstra – the main alternative suggested to rolling out fiber.

3. Wireless is cheaper / faster option

Not for mere mortals.  Additionally wireless may be theoretically fast, but my experience with wireless broadband is highly variable – and members of my family regularly have to roam their house looking for a good reception spot.  Speeds rarely reach the theoretical maximums quoted in press releases.  It may get faster, but 5x faster and with always on, trust with your life reliability?  I remain unconvinced.

4. We don’t need it.

This is the category I least understand.  This one seems to be from people who email once a week or who think the Internet is solely for Facebook.  Maybe its hard for people to imagine the kind of things this kind of bandwidth enables, but off the top of my head, here are some of the things the network would support:

  • Widespread telecommuting.  100Mbps is LAN speeds, this will make telecommuting a viable occurrence for not just the few, but any kind of information worker.  This could have a significant impact on greenhouse gas emissions and the centralized nature of our cities.
  • High Definition video communication (and crystal clear voice).  No more distorted telephone calls, less travel and fewer flights, closer connections with distant work mates, business partners, family and friends.
  • Pervasive Tele-medicine, Real time, high resolution medical imaging and remote diagnosis.
  • Video on Demand, The availability of subscriber specific IP TV will blow open digital media consumption.
  • The end of physical delivery of electronic goods (and subsequent transport, packaging, storage and cost).

It must be recognized that most of these  things can be done now (and are being done), but often with specialized equipment and sometimes at great expense. What this network makes possible is that these services will become utterly pervasive – and it is this pervasiveness where the impact lies.  When everybody is connected it will change the way Australia work, plays and communicates - and this will be as significant to our economy, our cities, our lives and our society as the advent of electricity.

Posted in Internet, Tech.

By Steven
April 8, 2009

2 comments

Why the Wiki <- What wiki’s offer

I wrote this for a colleague, but here it is for the world.  (At least I think I wrote it – it was a long time ago!)

Why the Wiki?

Typical challenges

It has always been a significant issue for large groups of people to successfully handle the creation, classification and discoverable storage of information.

The barriers for to creating information are many:

  • Getting staff to spontaneously document day to day procedures and outcomes is often difficult.
  • Staff are often frustrated by overly ornate requirements when creating information and feel efforts are wasted because their work cannot later be found by their peers.
  • Most people don’t have the time or the confidence to repeatedly publicize their work to peers or to distribute the information outside of their organisational area.
  • What is created is often hidden in directories which are not widely known or frequently accessed.
    Information creation can be compelled by procedure and regulated by process and thus it can become more likely to be created and managed.
    However, as organisational structure and personnel change over time, large quantities of valuable formal documentation are lost in forgotten locations and the organisation is condemned to re-learn, or re-document.

Typical response

The classic method of organising documentation is to use a hierarchical structure based on a shared location using common office productivity tools such as MS Word or MS Excel.
Hierarchical structures provide a mechanism by which large quantities of information can be structured into categories, with each branch offers a greater specialisation of its parent.

It can be argued that this structure however is more a function of the tools at hand since nested directory structures are a fundamental component of personal computing data management. It is no surprise then that this mechanism has become the dominant method for information storage.

The weakness of this approach is thus:

  • Not all information fits solely within a single category,
  • Categories require the development of an ontology, and its communication and training.
  • The same category names are rarely shared by many parties

An alternative response

In contrast to hierarchical directory structures is the concept of hyper linking, a method popularised in the World Wide Web.

The value of hyperlinking, when combined with a co-operative web creation environment results in a Wiki. A Wiki, (meaning Hawaiian for ‘Quickly’) has been described as:

“A solution that values information creation and cooperation over control and categorisation”

Wiki’s offer several advantages over traditional methods of creating and managing information.

  • The wiki allows arbitrary relationships between information.
    • A wiki page can be linked to any other wiki page, website or file system resource, allowing associates to be made between topics.
  • All content on the the Wiki is version controlled.
    • All wiki content, both wiki pages and attachments are version controlled, allowing you to see the when, who and what of change. Version control also allows the roll back of unwanted change and the recovery of deleted information
  • All content on the wiki is time-stamped
    • All changes to the wiki are time-stamped, so the exact time of change is known.
  • All content is associated with specific authors.
    • If configured to do so, all content is associated with an authenticated owner.
  • The wiki is searchable
    • All content, including attachments, is regularly indexed by the wiki’s inbuilt search engine, allowing relevant content to be discovered by search.
  • The wiki can be restricted
    • The creation and viewing of information can be restricted down to the page label specific groups or individuals and by the categories of creation, editing and deletion
  • The wiki can store any arbitrary file as an attachment
    • Some content is not suitable to be transcribed into something as basic as Wiki page, such data can be attached to the page by file upload
  • The wiki is web accessible
    • The wiki is accessible in a web browser and does not require (nor have) a desktop client.
  • The wiki can be reorganised.
    • Because of the nature of the wiki, barrier to re-organisation is low, with pages able to be relocated when needs and structure change.
  • The wiki notifies its users of change.
    • The wiki publicizes change, allowing users visiting to see new and changed information
  • The wiki allows you to monitor your content
    • The wiki allows you to establish a watch on content and receive email notification if it changes.
  • The wiki can assess the frequency of use
    • The wiki has basic inbuilt statistics that allow you to gauge the frequency of use of information.
      With all these benefits in mind, Wiki’s do have some advantages.
      Limitations of the wiki
  • The wiki does not offer complex word processing functionality
    • The Wiki is not an appropriate choice for longer (> 1 page) or complex, formal documents.
  • A successful Wiki’s is as much a point of view as a tool.
    • Successful use of a Wiki is associated with staff understanding the point of view of ‘impulsive’ documentation creation.
  • Wiki’s can appear alarming to those unfamiliar with the concept.
    • Most organisational approaches to information emphasis control and restriction over freedom of action, it can be confronting to some that the Wiki’s default point of view is to allow anyone to create or edit (and this often causes the audit and version control capabilities to be overlooked)

Posted in Tech.

By Steven
April 2, 2009

No comments

IBM to buy Sun, what about Dell?

So, the WSJ is reporting that IBM is in talks to acquire Sun Microsystems for 6.5 billion (a considerable premium on its market valuation).

Some analysis of the news labeled this story red herring, put out there by Sun to get the scare on the real buyer, I tend to agree.

Besides securing Java I don’t understand what IBM gets out of buying Sun.

IBM would be buying a company who’s stack of software/hardware goes head to head with most of IBM’s existing and well established brands. I can’t see this gives IBM anything but a headache and could confuse IBM customers.

For IBM, it would be come an issue of ‘How can you push your high end enterprise hardware/software and its pricing structure against a FOSS stack from your new subsidiary’.  Any FUD (Fear, Uncertainty and Doubt) they could spread about Sun’s viability and software capability is immediately compromised and they run the real risk of cannibalizing their own sales across a lot of areas.

The second possibility it that its an acquisition focussed on killing off Sun for competitive reasons.  Assuming the regulator has no issue with that (which seems unlikely), then its tacit acknowledgement that Sun strategy is working.  If its working well enough that IBM is wanting to spend $6.5 billion to stop it, why would Sun sell out?

Finally, IBM could be moving to secure Java.  This may only sound practical to Java development community, but with its own JVM and the JDK open sourced most of what I see IBM can bring is their checkbook.  In general spirit, the community is walking, if not running away, from the kind of software ecosystem IBM represents (Eclipse not withstanding) – and surely they could provide that influence a lot cheaper than the cost of acquiring Sun.

What about Dell?

A commenter on one article noted that the real buyer could be Dell and on first glance this seems like a more plausible idea.

Dell is one of the only big names in the desktop/server business which doesn’t have a high end enterprise arm or a software infrastructure stack (the only one I can think of is Lenovo, who I assume still partners strongly with IBM).

Dell is likely already have a presence in the data centers and offices of Sun’s customers via their Laptop/Desktop/Intel servers.

Dell gets the opportunity to sell services across the whole of the data center rack with an enterprise server line + processor architecture, a storage array business, an operating system that can take an organization from the desktop to the cloud and a software stack running the gamut from Operating System to Word Processing (And perhaps in emerging markets like China, this matters).

Sun gets access to a volume sales channel and commodity Intel hardware – something that their software stack could thrive on.

Does that seem more logical to you?

Posted in Tech.

By Steven
March 19, 2009

1 comment