<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-7577482648357005498</id><updated>2024-09-24T20:52:35.708-04:00</updated><category term="android"/><category term="acs"/><category term="cloud"/><category term="computing"/><category term="development"/><category term="future"/><category term="groovy"/><category term="kanban"/><category term="m4u"/><category term="mobile"/><category term="process"/><category term="sandbox"/><category term="script"/><category term="secure"/><category term="tools"/><category term="transcode"/><title type='text'>Positively Disruptive</title><subtitle type='html'>Insider&#39;s perspective on software that changes our world</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>11</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-2205897191560722072</id><published>2012-05-22T20:58:00.000-04:00</published><updated>2012-05-22T20:58:01.298-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="development"/><category scheme="http://www.blogger.com/atom/ns#" term="kanban"/><category scheme="http://www.blogger.com/atom/ns#" term="process"/><category scheme="http://www.blogger.com/atom/ns#" term="tools"/><title type='text'>Cool Tool : KanbanFlow</title><content type='html'>I was looking for a simple &lt;a href=&quot;http://en.wikipedia.org/wiki/Kanban&quot; target=&quot;_blank&quot;&gt;Kanban&lt;/a&gt; tool for the past 2 years now. No need for complex features, just the minimum: columns, activities and flexible constraints. I finally found it : &lt;a href=&quot;http://kanbanflow.com/&quot;&gt;http://kanbanflow.com&lt;/a&gt;&amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
I&#39;m a fan of small teams. If you read my blog, you&#39;ll quickly see that I don&#39;t believe in large software projects and that, all projects should be split into teams of ideally three (3) members. Some will say that&#39;s too small, but put together three (3) talented developers, one having good design skills, another having good sysadmin skills, with a good team leader/architect/visionnary/good guy and you can overcome most challenges. So, for me, a a simple tool is what we need most of the time to avoid loosing tasks, avoid accumulating unfinished work and avoid management overhead.&lt;br /&gt;
&lt;br /&gt;
I&#39;ve been using KanbanFlow for 3 weeks now, and it does exactly what it must do for me. I create task in a swinlane and move it as we finish it until it goes to production. We have constraints on the &quot;In Progress&quot; swimlane to &quot;team size +1&quot; which enables us to either park (move the story back to the previous swimlane) a story or push it for deployment. There&#39;s no middle state. It&#39;s planned or done, never partially done (at least in our planning).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/2205897191560722072/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/05/cool-tool-kanbanflow.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/2205897191560722072'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/2205897191560722072'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/05/cool-tool-kanbanflow.html' title='Cool Tool : KanbanFlow'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-3363681545611441325</id><published>2012-05-03T09:45:00.000-04:00</published><updated>2012-05-03T09:45:56.916-04:00</updated><title type='text'>How software companies hi-jacked the web</title><content type='html'>&lt;br /&gt;
&lt;div class=&quot;p1&quot;&gt;
One debate that amused me a lot in the past years was the nearly religious fight between &lt;a href=&quot;http://en.wikipedia.org/wiki/REST&quot; target=&quot;_blank&quot;&gt;REST&lt;/a&gt; and &lt;a href=&quot;http://en.wikipedia.org/wiki/SOAP&quot; target=&quot;_blank&quot;&gt;SOAP&lt;/a&gt;. I’ll use this example to demonstrate how deep in our mind is anchored the application concept. How deeply we think as offline beasts, even when we talk about things like cloud computing and web APIs.&amp;nbsp;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;I won’t cover what each approach is here, you’ll find plenty of good (and bad) analysis and comparisons everywhere. The point is that people are arguing about which one is the best, mostly based on factors like speed, security and complexity.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;And they completely miss the point.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;SOAP is the paramount of the classic application model taking control of the Internet, not the Web. Because, even if SOAP uses technologies like XML and HTTP, it uses them as to create a closed protocol, without much concerns about the nature of the Web itself. In the SOAP world, you connect two applications together just like you do with TCP sockets. It’s great that the network be worldwide, but at the end of the day, we’re talking about integration that could have been performed with a binary protocol without much losses.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;The premise behind SOAP is that you have (at least) two software entities that needs to communicate together. You need to exchange messages, with potentially complex sequences and orchestration conditions. So SOAP is used to bridge different universes and, with the diversity of applications out there, it comes to no surprise that SOAP may become a complex protocol to ensure it covers the most cases.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;There were great promises with SOAP at the turn of the century. Self discovery of information services, self-describing their capabilities and letting the other discover the best service at development time or even at runtime. Most of these promises were put aside when the different standard committees discovered the immutable limitations of the application model. It’s hard to design a standard that will bridge different worlds, translate realities with minimal common semantic. That was doomed from the start and billions of investment later (by so many companies), they resigned and decided that SOAP was another EDI, an integration protocol with some great and not-so-great features.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;So, people decided that REST was a better &lt;i&gt;protocol&lt;/i&gt;... and again, with our offline application background, the decision wasn’t made for the good reasons! REST is simpler, less overhead, you just have to send XML or JSON payload over HTTP and uses standard HTTP verbs and &lt;i&gt;voilà! &lt;/i&gt;You get a powerful integration protocol and the Web API era was born.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;But again we missed the point. Worst then that, we increased the confusion and postpone the real decisions that would help us save tons of money on information management. Web APIs are flawed by design. They may call themselves RESTful, but few of them really are, sadly. The Web doesn’t need an API. The Web shouldn’t require integration technologies. We hi-jacked the Web concept fifteen years ago and created and diverted a number of technologies to workaround the weaknesses of our model. We need to get back to the essence of the Web and quickly.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;The root of the problem is the concept of web application itself. While the initial Web was based on sites, they were a transparent structure exposing resources representations. The essential elements were the resources themselves, not the site hosting them. With our need to control ($), with our offline thinking and with all our theories geared at building &lt;i&gt;programs&lt;/i&gt;, it was natural that we just replicate this model on the Web. So we used the Web as a new distribution mechanism, a network of applications, each based on the same foundations, asking their own passwords, existing in their own reality. I’ve seen web applications without a single hyperlinks and even worst, I’ve seen people preventing the use of hyperlinks! It was creating side-effects in their application logic! How many tricks have you seen to manage the famous back button of the browser?&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;So, if we had seen REST as an architectural approach to expose autonomous resources, regardless of application contexts, there would never have been a debate on which technologies was the best integration tool. If we hadn’t analyze the situation with our &lt;i&gt;application mind,&amp;nbsp;&lt;/i&gt; we would never have compared REST to SOAP.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;We’re past the time where we had the luxury to re-invent the wheel, to host our own universes. The moment we’ll stop thinking about &lt;i&gt;integrating&lt;/i&gt; web applications and think about &lt;i&gt;hyperlinking&lt;/i&gt; information and logic, will start reducing system complexity, save money we can greatly use elsewhere. We have to stop thinking in application terms and create autonomous resources, assembled from a million different web sites, each one being consumed through micro-transactions, sharing common semantic in a common universe which is the Web.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
So for those who think that &lt;a href=&quot;http://www.wired.com/magazine/2010/08/ff_webrip/all/1&quot; target=&quot;_blank&quot;&gt;the Web is dead&lt;/a&gt;... you better redo your homework...&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;-- The network is the computer... Vision is one thing, timing is everything.&amp;nbsp;-- &lt;a href=&quot;http://en.wikipedia.org/wiki/John_Gage&quot; target=&quot;_blank&quot;&gt;John Gage&lt;/a&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;a href=&quot;http://geeknizer.com/rest-vs-soap-using-http-choosing-the-right-webservice-protocol/&quot; target=&quot;_blank&quot;&gt;A classic comparison&lt;/a&gt; of REST versus SOAP, seen from the application perspective.&amp;nbsp;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/3363681545611441325/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/05/how-software-companies-hi-jacked-web.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/3363681545611441325'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/3363681545611441325'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/05/how-software-companies-hi-jacked-web.html' title='How software companies hi-jacked the web'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-8182093366531949390</id><published>2012-04-30T09:00:00.000-04:00</published><updated>2012-04-30T09:00:04.935-04:00</updated><title type='text'>The Future of Computing (Part 2)</title><content type='html'>&lt;br /&gt;
&lt;blockquote class=&quot;tr_bq&quot;&gt;
&lt;span class=&quot;s1&quot; style=&quot;font-weight: normal;&quot;&gt;&lt;i&gt;Mobile and pervasive computing are trends that will shape the next 20 years and, while we can’t figure out exactly the form our devices will take (if there will be devices at all!), we can be sure that we won’t have to rest on our fat bottoms to indulge in our favorite computing activity.&amp;nbsp;&lt;/i&gt;&lt;/span&gt;&lt;/blockquote&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;Like all evolving technologies, we first root it in what we know, in our current reality. This is a normal&amp;nbsp;behaviour, even more in the context where most startups get funded to add a simple brick to our computing wall. While there are plenty of mobile variations, the primary theme has been established by Apple with the iPhone. Few may argue against it, given the success of the App Store and the iOS platform. But, even as a proud iPad owner, I can’t see how this platform could strive in a world where all computing operations were to be performed on the move. Today, we’re kind of helping the platform by selecting the use cases that are the most adapted to the capacity of the device, but in a world where no other computer would exist, how could we go with operating our businesses with such devices?&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;All mobile platforms have adopted the (broken?) application model of classic operating systems. The only partial exception to that is Android with its &lt;a href=&quot;http://developer.android.com/reference/android/app/Activity.html&quot; target=&quot;_blank&quot;&gt;Activity model&lt;/a&gt;, but because people see all solutions as apps, they don’t deliver half the power they could. The major problem with the app model is that we have to envision how our user will use them and make provisions during their development to cover what we think will be the real value generating cases. Historically, when the app model was created, it was easier because the usage context of the target app was not changing that much. You had less inputs, the user was sitting in a room where computing services and devices were controlled and predictable. You could relatively easily foresee how your application would be used and develop a software program to serve it.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;With mobility, we’re now in what I would call a &lt;i&gt;variable usage context&lt;/i&gt;, where your application can be used in a myriad of different contexts and expected to adapt for the user to be satisfied. For example, we see a lot of location-aware applications. You’re search results will vary according to where you are. We see applications listing nearby people/friends, businesses and more. This is a start but far from enough to support our future computing needs. We need to interact with these surrounding elements, we need to integrate them in our application logic. We need our application to adopt these proximity services as if they were part of it. This is not very compatible with our current analysis/design approach in software projects. Other factors must also be taken into consideration, like the time of the day, the weather, the current goals of the user: is he going to a business meeting or just wandering around looking for a nice spot to have drink? Understanding and integrating this usage context in a solution will be critical if mobility has to become the only computing way.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;These additional factors must be integrated in our solutions mostly because of the limited input capabilities of our mobile devices and also, of the very nature of mobility where we’re most likely being doing something else which prevent us from concentrating for a long time. Mobile computing should be fundamentally task-oriented, making sure users may quickly select from a minimal list of potential actions, all determined by the current usage context. The completion of these tasks will most likely requires the use of surrounding services and a certain personal context that will imply the semantic of the commands and actions. As a mobile user, you’ll want to quickly ask for the next bus stop time, without having to install an app, create an app-specific account and look for the closest bus stop. While you could do it in your hometown with the current application model, chances are the bus will have passed by the time you installed and configured everything while traveling!&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;Apple’s SIRI is a good early example of a task-driven approach spanning multiple applications and good step forward to push users away from the classic application model. But SIRI’s limitations are the same than most recognition or artificial intelligence technologies: they have difficulty performing outside a very well scoped context. This is to a certain point normal and will continue to improve as we go. But the effort to increase the scope of these technologies is far from linear in the current computing paradigm. The problem will need to be attacked from a different perspective if we want desktop computers to be things of the past.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;br /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/8182093366531949390/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/04/future-of-computing-part-2.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/8182093366531949390'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/8182093366531949390'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/04/future-of-computing-part-2.html' title='The Future of Computing (Part 2)'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-4000253132688439602</id><published>2012-04-27T10:39:00.002-04:00</published><updated>2012-04-28T10:08:32.355-04:00</updated><title type='text'>The Future of computing (Part 1)</title><content type='html'>&lt;br /&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;What’s the future of computing? Where are the next disruptive technologies that will change the way we manage our information? You might say that the 80s were the years of the PCs (including LANs), the 90s were the years of the Web, the naughties where the years of the social networks, what will the next decennia bring us?&amp;nbsp;Mobility? Pervasive computing? Artificial Intelligence (finally!)?&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;It is always hard to play predictions but while we can’t predict the name of the company that will dominate the next twenty years, we can most certainly state that it doesn’t exist yet. We can also establish a few strong trends that will help us create a rough portrait of what computing will look like and thus, what kind of technologies might be useful in the coming years.&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;My goal in exploring these new trends is to underline the necessity to rethink the way we approach software. We continue to have a high rate of software project failures and that won’t improve as solutions complexity is skyrocketing. When I look at the available operating systems, I see a few cosmetic changes, but no significant improvements to reflect the profound transformation of our computing habits in the past ten years. When I see my children using computers, I can clearly see that the current approach to software, the application model that we use, isn’t going to fulfill their computing expectations. They need much more flexibility, more semantically significant abstractions and a fully personalized experience. They are computer-literate enough to take in charge the last miles of any solutions, mix and match information elements to please their needs instead of a rigid, pre-packaged applications.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;Rethinking software will mean forgetting about things we consider immutable and take a new perspective to problems we thing we&#39;ve already solved. We&#39;ve come a long way in a very short period of time. The foundations on which we build all our software today were put in place with a much different world in mind. I&#39;m not saying that we have to throw everything off the window, I&#39;m just saying that we need to review the way we conceive software; the very nature of a software application, being a classic, web or any kind of distributed packaged code unit. We still think in &lt;i&gt;offline&lt;/i&gt;&amp;nbsp;mode, even when we build cloud systems. Think about it, software is still an &lt;i&gt;offline&lt;/i&gt; activity, built on a machine, bundling a large number of hypotheses and preconditions about how it will be used when &lt;i&gt;pushed to production&lt;/i&gt;. Software must be living, constantly evolving and adapting to each user context and the task at end. Science-fiction? Complexity is a matter of perspective...&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;In parallel, you may follow my experimentations on my cloud-era operating system on &lt;a href=&quot;https://github.com/jgrenon/galakc&quot; target=&quot;_blank&quot;&gt;Github&lt;/a&gt;. It&#39;s a little bit early to fork, but don&#39;t hesitate to contact me if you&#39;re interested in contributing, I&#39;ll be putting a team in place soon.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p1&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class=&quot;p2&quot;&gt;
&lt;span class=&quot;s1&quot;&gt;&lt;/span&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/4000253132688439602/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/04/future-of-computing-part-1.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/4000253132688439602'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/4000253132688439602'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2012/04/future-of-computing-part-1.html' title='The Future of computing (Part 1)'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-6493812322344746770</id><published>2011-07-27T00:43:00.000-04:00</published><updated>2011-07-27T00:43:34.027-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cloud"/><category scheme="http://www.blogger.com/atom/ns#" term="groovy"/><category scheme="http://www.blogger.com/atom/ns#" term="sandbox"/><category scheme="http://www.blogger.com/atom/ns#" term="script"/><category scheme="http://www.blogger.com/atom/ns#" term="secure"/><title type='text'>Scripting in the cloud</title><content type='html'>I decided to push a little bit more regarding executing script code in a shared server environment. For our Ambient Vibes platform, we&#39;re looking at letting user/developer create pattern sensors that will trigger an action based on certain patterns in a given user Vibes (a stream of business events). Actions may be anything as we dont&#39; want to restrict to specific ones. So, naturally, the solution is to execute a script in the context of the given user. It&#39;s working well at the moment, we&#39;ve selected the Groovy language, which is compatible with our Java VM and offer good support to write high-level DSLs to help users describe what they want to do instead of programming it.&amp;nbsp;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;But the barrier to opening Ambient Vibes to the public, is our incapacity, at the moment, to easily monitor script execution to detect misbehaving scripts and kill them. Of course, scripts run within a very limited sandbox, thanks to the solid security foundation inherited from the Java platform. But, while we may control the classpath, control what code can be executed, what resources may or may not be accessed by the script, we&#39;re still pretty open to dumb scripts performing tight loops, allocating tons of memory and other good jokes like these. By the very nature of our system, we let unsecured scripts enter our application space and we have to keep them secure.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;This is why we launch the Kevlar project with the goal to enable easy embedding of Groovy scripts within a monitored and secure environment. Our goal is to let developer configure the Kevlar Groovy shell to listen to specific events (high memory allocation for example) and respond accordingly (prevent the allocation, log a warning, etc).&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;Our goal is to gradually enhance our protections to include all memory or cpu &quot;attacks&quot; and also add a complete permission system , like Android, to control imports, or access to declared services. Our goal is to inject all indicated resources in the script environment and control its execution.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;For now, you may track the evolution of project Kevlar through this blog. We&#39;ll setup a GitHub project soon.&amp;nbsp;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/6493812322344746770/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/07/scripting-in-cloud.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/6493812322344746770'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/6493812322344746770'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/07/scripting-in-cloud.html' title='Scripting in the cloud'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-1295131785272200527</id><published>2011-05-09T08:40:00.000-04:00</published><updated>2011-05-09T08:40:30.225-04:00</updated><title type='text'>JQuery Mobile Ajax Caching</title><content type='html'>JQuery Mobile is a very good mobile UI framework. I use it for mobile version of web sites or in conjunction with PhoneGap to create portable mobile apps. One interesting aspect of the framework is that you can mix and match local and remote pages. JQM seamlessly loads any remote pages from your server as if it was on the page. It&#39;s a cool feature.&lt;br /&gt;
&lt;br /&gt;
By default, the first time the page is loaded but further times, it is cached locally for performance. This is causing issues with dynamic content. For example, I have a Google Maps on a page and it&#39;s being shown only the first time. I get old pages with wrong state, pretty annoying.&lt;br /&gt;
&lt;br /&gt;
Documentation state that you may disable ajax loading in mobileinit bootstrap function, but doing this, you disable ALL ajax for all pages, which is not usually what you want.&lt;br /&gt;
&lt;br /&gt;
The real solution was proposed in this &lt;a href=&quot;http://forum.jquery.com/topic/using-jqurey-mobile-without-the-ajax-caching-stuff&quot;&gt;post&lt;/a&gt;&amp;nbsp;and has been very helpful for me than. Just add this code in your primary HTML page (the one that is initially loaded when you start, index.html?)&lt;br /&gt;
&lt;pre style=&quot;background-image: URL(https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4AKIN28oh2PYHOMA83AVH7AsI4hZyjmlH-UXKydWrvOGwOVtJ3SHA4yzWY1F-RSQiravB_GuA2Qgp4Glu6l77ayR6aQaBJ2TsSu8CARicA_sQJkPPmvEfZNR6dbwde17d-Tgs6reP2361/s320/codebg.gif); background: #f0f0f0; border: 1px dashed #CCCCCC; color: black; font-family: arial; font-size: 12px; height: auto; line-height: 20px; overflow: auto; padding: 0px; text-align: left; width: 99%;&quot;&gt;&lt;code style=&quot;color: black; word-wrap: normal;&quot;&gt;      $(function(){  
           $(&#39;div&#39;).live(&#39;pagehide&#39;, function (event, ui) {  
             var $this = $(this);  
             if ($this.attr(&#39;ID&#39;) !== undefined &amp;amp;&amp;amp; $this.attr(&#39;data-cache&#39;) !== undefined &amp;amp;&amp;amp; $this.attr(&#39;data-cache&#39;) == &quot;never&quot;) {  
               var page = $this.attr(&#39;ID&#39;);  
               $(document.getElementById(page)).remove();  
             }  
           });  
      });  
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
With this code, you can now control caching on a per-page basis by adding &lt;b&gt;data-cache=&#39;never&#39;&lt;/b&gt; to your page div.</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/1295131785272200527/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/05/jquery-mobile-ajax-caching.html#comment-form' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/1295131785272200527'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/1295131785272200527'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/05/jquery-mobile-ajax-caching.html' title='JQuery Mobile Ajax Caching'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-5102112597025145867</id><published>2011-03-14T19:51:00.001-04:00</published><updated>2011-03-19T08:09:02.005-04:00</updated><title type='text'>Upcoming Play Framework 1.2</title><content type='html'>Those who think Java is dead may not be aware of the wonderful web framework developed by Guillaume Bort and his team: Play! I&#39;ve been using it for more than one year now and I have to say that this is by far the most productive framework I&#39;ve seen. I&#39;ve used all Java frameworks (yes all!) in quest of fast build-cycles, easy testing and a complete yet not closed stack where I could concentrate on generating business value instead of messing with underlying dependencies. Play! is fast to learn (good doc) and you get to find advanced features available, easy to use, well packaged, each time you need something.&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;In &lt;a href=&quot;http://groups.google.com/group/play-framework/msg/ed1cae8ab39f15a8?pli=1&quot;&gt;this post &lt;/a&gt;on their forum related to the upcoming Play! 1.2, Guillaume advertise a number of asynchronous features with the same user friendliness and nice packaging we&#39;ve expected from Play! Play was already a nice solution for asynchronous web request processing, but with 1.2, they integrate WebSockets, a better continuation support and various other constructs that will make your life easier and your app incredibly fast and lightweight.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;If you&#39;re a Java developer and you need to create a powerful web site (including web services, json, xml and any RESTFul) give Play! a try!&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/5102112597025145867/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/03/upcoming-play-framework-12.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/5102112597025145867'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/5102112597025145867'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2011/03/upcoming-play-framework-12.html' title='Upcoming Play Framework 1.2'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-4705253963775053975</id><published>2010-08-18T11:14:00.002-04:00</published><updated>2010-08-22T15:33:52.059-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="android"/><category scheme="http://www.blogger.com/atom/ns#" term="computing"/><category scheme="http://www.blogger.com/atom/ns#" term="future"/><category scheme="http://www.blogger.com/atom/ns#" term="mobile"/><title type='text'>Computing Fragmentation</title><content type='html'>With the rapid growth of intelligent phones and other mobile computing devices, the Internet is more and more used on the go. Morgan Stanley analysts &lt;a href=&quot;http://mashable.com/2010/04/13/mobile-web-stats/&quot;&gt;predict&lt;/a&gt; that the mobile web will be bigger than the desktop web by 2015. I think that’s a believable projection, I would even say that it may be even faster.&lt;br /&gt;
&lt;br /&gt;
From the computing side, we need to go farther than the mobile or not concerns and understand what patterns of computing will emerge from this new paradigm. If you look at the computing trends of the past 30 years, people were installing applications and performing all separate tasks in each one. These limitations were often due to the lack of communication capacity and the way applications were distributed. But in the mobile web, people connect to the Internet, get whatever they need for a specific task and jump to the next. Our computing devices are more and more task or activity oriented (like Android), letting people assemble their applications as they need, for the current requirements.&lt;br /&gt;
&lt;br /&gt;
We see the same thing with web sites. You go to google, than google maps, than view photos in Flickr or video in Youtube, get a tips from Yelp and make a reservation using another web site. Web sites are more and more task oriented, integrating for the time of a transaction, to fit the current user needs. For me, this is where computing is going. Our mobile devices will become our assembling tool to create applications on the fly based on the task we want to achieve. We must think of our web applications as components in this big realtime application assembling game. Current mashup technologies are a good start toward supporting this, but they need to improve semantically and they most be extensible and customizable on a transaction basis.&lt;br /&gt;
&lt;br /&gt;
The mobile web is a realtime, personal, task-driven experience. For now, we’re mobile, with a glimpse of task orientation emerging on certain devices.&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/4705253963775053975/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/computing-fragmentation.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/4705253963775053975'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/4705253963775053975'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/computing-fragmentation.html' title='Computing Fragmentation'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-9068575233059160079</id><published>2010-08-09T15:42:00.000-04:00</published><updated>2010-08-09T15:42:22.048-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="acs"/><category scheme="http://www.blogger.com/atom/ns#" term="android"/><category scheme="http://www.blogger.com/atom/ns#" term="m4u"/><category scheme="http://www.blogger.com/atom/ns#" term="transcode"/><title type='text'>ACS Transcode Sample available</title><content type='html'>Following &lt;a href=&quot;http://positivelydisruptive.blogspot.com/2010/08/streaming-m4a-files-using-android-cloud.html&quot;&gt;my post&lt;/a&gt; on transcoding media files on the cloud with ACS, I&#39;m happy to announce that you can now download the Transcode sample&amp;nbsp;&lt;a href=&quot;http://github.com/Pyxoid/acs/tree/master/samples/transcode/&quot;&gt;source code&lt;/a&gt; and connect to ACS to transcode M4A files. To build the application, you just need to clone the ACS repository in your workspace using GIT and import acs-protocol, acsclient and transcode in Eclipse (or your preferred IDE). Of course, you need Android SDK and a 2.2 phone or emulator.&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;You can install the cloud-phone from the cloned GIT repo or simply install the latest production version from the Android market. You will be prompted to create a free account and as soon as your cloud-phone is connected, you&#39;re ready to transcode!&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;Keep in mind that ACS is still pretty young and you may encounter a few failures here and there. Just stop and restart the service from the CloudPhone status activity and tell me what happened!&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/9068575233059160079/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/acs-transcode-sample-available.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/9068575233059160079'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/9068575233059160079'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/acs-transcode-sample-available.html' title='ACS Transcode Sample available'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-3172469012712964581</id><published>2010-08-09T00:43:00.001-04:00</published><updated>2010-08-09T00:45:22.930-04:00</updated><title type='text'>Mixin in Java using Groovy</title><content type='html'>I&#39;m a big fan of the Groovy language. There are many new dynamic languages for the JVM, but for me, Groovy is the most natural one, simple yet very powerful. A powerful aspect of Groovy is that, even if you&#39;re not coding your classes in Groovy, you can &lt;i&gt;groove&lt;/i&gt; your Java code. Have a look at how simple it is to add a mixin to a Java class :&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;class MyClass {&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&amp;nbsp;&amp;nbsp;public getVal1() { return 5; }&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;@Category&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;class ExtraBehavior {&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&amp;nbsp;&amp;nbsp;private String extra;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&amp;nbsp;&amp;nbsp;public void setExtra(String extra) { this.extra = extra; }&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&amp;nbsp;&amp;nbsp;public String getExtra() { return &quot;extra&quot;; }&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/div&gt;&lt;div&gt;Now, you apply Groovy magic :&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;DefaultGroovyMethods. mixin( MyClass.class, ExtraBehavior.class);&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;After this point, the getExtra method will be available from myClass instances. To set the extra value, just use the metaclass :&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;GroovyObjectSupport.class.cast(anyInstance).getMetaClass().setProperty(anyInstance, &quot;extra&quot;, &quot;newVal&quot;);&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;When calling anyInstance.getExtra ( using Reflection of course), you&#39;ll access the ExtraBehavior getter and internal state. Pretty cool stuff to inject behavior and state at runtime in your Java classes.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/3172469012712964581/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/mixin-in-java-using-groovy.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/3172469012712964581'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/3172469012712964581'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/mixin-in-java-using-groovy.html' title='Mixin in Java using Groovy'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7577482648357005498.post-5403425835810360507</id><published>2010-08-08T23:19:00.000-04:00</published><updated>2010-08-08T23:19:58.846-04:00</updated><title type='text'>Streaming M4A files using Android Cloud Services</title><content type='html'>&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;I was surprised, when developing a streaming music player for the Android phone, to discover a strange limitation. The platform Media Player is able to stream MP3 files (and many others), but M4A files (unprotected iTunes files) must be downloaded to the device before being played. After reading a few threads about this problem, I decided to apply ACS cloud capacity to solve this problem.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;About ACS&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;ACS stands for Android Cloud Services (http://www.androidcloudservices.com). This is a young cloud platform specialized for the Android platform on which I&#39;m working right now. The goal is to extend the phone (or any Android device) capacity through tight integration with cloud resources. As of now, we&#39;re able to create cloud AsyncTask, Service, integrate storage and additional memory. This is still in early alpha, but stable enough to be used if you&#39;re not afraid of the unknown!&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;ACS Transcoding&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;ACS components executing in a cloud thread have access to the ACS framework, which exposes various tools like facebook &amp;amp; twitter access, YQL, S3 and various useful other tools not natively available on your Android device. We&#39;ll be using two of these tools to solve our streaming problem : Web and Media tools.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;div style=&quot;font-family: Times; font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;The Transcoder class&lt;/span&gt;&lt;/div&gt;&lt;div style=&quot;font-family: Times; font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;After having integrated the acs-client library and configured your application (see the &lt;a href=&quot;http://github.com/Pyxoid/acs/tree/master/samples/transcode/&quot;&gt;Transcoder sample code&lt;/a&gt; for more details), you need to create your transcoder client class in the assets folder.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style=&quot;font-family: Times; font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt; &lt;/span&gt;&lt;/div&gt;&lt;div style=&quot;font-family: Times; font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: small;&quot;&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;class Transcoder extends ScriptComponent &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;/**&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; * Transcoding implementation&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; */&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;def transcode(String sourceUrl) &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;// Instantiate a transcoding task&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;def task = new TranscodingTask(cloudDevice:cloudDevice, sourceUrl:sourceUrl, format:&#39;mp3&#39;)&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;// Register this transcoding task on provided task server for single use (no timeout)&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;cloudDevice.web.register(&quot;audiotranscode.mp3&quot;, task, true)&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;}&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;/span&gt;&lt;/div&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;It exposes a single method with the sourceUrl of the M4A file and returning (implicitly) a new URL where the transcoded content will be available. As you can see, we use the cloudDevice object to access various framework tools. The register method of the &lt;b&gt;web&lt;/b&gt;&amp;nbsp;tool will create a temporary URL usable once by the phone running the ACS application. This is a convenient way to expose modified content to your phone from the web. This could be used to post-processed picture, videos, web pages and much more.&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;The transcoding task is built over the ACS Media tool and will executed when ACS received an HTTP GET request to the provided URL.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Lucida Grande&#39;; font-size: small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 11px;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: x-small;&quot;&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;class TranscodingTask {&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;def sourceUrl&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;def format&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;def cloudDevice&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;/**&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; * request.params contains all parameters&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; * response.out is used to output our response&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; * Use the internal audio tool to perform the actual transcoding&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; */&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;void execute(def request, def response) &amp;nbsp; &amp;nbsp; {&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;// Indicate the audio type of our stream &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;response.addHeader(&quot;Content-Type&quot;, &quot;audio/${format}&quot;)&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;cloudDevice.mediaEngine.transcode(sourceUrl, format, response.outputStream)&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;}&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;The single execute method will receive the request and response from the HTTP server. The rest is simply set the right content type and call the transcode method from the ACS media engine. The transcode method will read the source media and will write the transcoded result directly to the HTTP request output stream. Easy.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: medium;&quot;&gt;Using the Transcoder&lt;/span&gt;&lt;/div&gt;&lt;div&gt;To execute this transcoding code in the cloud, we have to use ACS from our Android application. By using the standard CloudDevice service, you create a cloud execution context around your Transcoder implementation like this :&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;// Establish the scripting context for the transcoder&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mTaskImpl = mDevice.createExecutionContext(&quot;audioTranscoder&quot;, this, TranscoderImplementation.class, BaseExecutionContextHandler.class);&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: inherit;&quot;&gt;The mTaskImpl member is now a proxy to your cloud implementation. Just call mTaskImpl.transcode with the source url in parameter to execute your transcoder.&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;div&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;public URL transcode(URL sourceUrl) throws IOException &amp;nbsp; &amp;nbsp; &amp;nbsp;{&lt;/div&gt;&lt;div&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/div&gt;&lt;div&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;// Delegate the execution to our task implementation&lt;/div&gt;&lt;div&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;return new URL(mTaskImpl.transcode(sourceUrl));&lt;/div&gt;&lt;div&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;As you can see, using cloud resources with ACS is really simple and feels native in your Android applications. You can now integrate the whole thing in the Media Player like this :&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;// Create our transcoder instance&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mTranscoder = new Transcoder(mDevice);&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer = new MediaPlayer();&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer.setOnBufferingUpdateListener(mBufferingListener);&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;try {&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;// Retrieve the transcoding URL from our transcoder&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;URL transcodedUrl = mTranscoder.transcode(new URL(mSourceUrl.getText().toString()));&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&lt;br /&gt;
&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;// Configure the media player for streaming as usual&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer.setDataSource(transcodedUrl.toString());&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer.setAudioStreamType(AudioManager.STREAM_MUSIC);&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer.prepare();&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;mMediaPlayer.start();&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;} catch (Exception e) {&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;&amp;nbsp;&amp;nbsp; Log.e(LOG_TAG, &quot;Unable to transcode media, e&quot;);&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-family: &#39;Courier New&#39;, Courier, monospace;&quot;&gt;}&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;You&#39;re now able to stream any content in your Android by using ACS to transcode your media in real time in the cloud. ACS Media is built over the powerful ffmpeg, so we support about any audio and video transcoding. You can get more details about ACS on the &lt;a href=&quot;http://www.androidcloudservices.com/&quot;&gt;web site&lt;/a&gt;&amp;nbsp;or visit &lt;a href=&quot;http://www.github.com/pyxoid/acs&quot;&gt;GitHub&lt;/a&gt; to download the code and start integrating the cloud in your Android!&lt;/div&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://positivelydisruptive.blogspot.com/feeds/5403425835810360507/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/streaming-m4a-files-using-android-cloud.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/5403425835810360507'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7577482648357005498/posts/default/5403425835810360507'/><link rel='alternate' type='text/html' href='http://positivelydisruptive.blogspot.com/2010/08/streaming-m4a-files-using-android-cloud.html' title='Streaming M4A files using Android Cloud Services'/><author><name>Anonymous</name><uri>http://www.blogger.com/profile/05310053305489035842</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>