MobDevCon 2014 Survey

As many of you know, this year’s MobDevCon had to be cancelled just weeks away from the conference. We wanted to release a statement to let those that had reserved tickets for the conference and were looking forward to the conference following on from the huge success of last year’s MobDevCon 2013, know the reason behind the event being cancelled. Unfortunately, even after extending the early bird tickets at reduced prices, and the sale of tickets for a further working week, there were only 10 paying delegates confirmed to attend. Add to this the sponsors, speakers and organisers this figure did rise to 40 people however we wanted to protect our relationships with the confirmed sponsors and it’s important to us to deliver on our promises. Having predicted around 100 paying delegates we felt that this would not present our sponsors with a fair return on their sponsorship investments. The low numbers of paying delegates also meant that the revenue generated from the conference would not cover its breakeven point and proved to be an unfeasible proposition for Naked Element Ltd. to undertake.

As we’ve mentioned last year’s conference was a resounding success and we’d like to hear from you, as past attendees or members of the mobile development community, how we can make the conference a success once more and try to address the reasons behind poor ticket sales. We’ve had fantastic feedback from previous conferences and have the passion and commitment to bring the latest in mobile developments to the area and feel that there’s still life in our Mobile Development Conferences.

We would really appreciate if you would take just 1 minute out of your day to answer our questionnaire. All responses will be anonymous unless you specify otherwise and responses will be held in strict confidence. We will be taking your valuable feedback into account when organising future conferences and this will enable us to deliver what you want, how and when you want it.

Complete the questionnaire: https://www.surveymonkey.com/s/J9WT5KJ

Comments

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...

Paul Grenyer

Search This Blog