Before the second meeting, Maradona hesitated to the press with a possible exit (he made a joke with the sponsor of the club Mars and ‘Marseille’) while Tapie harassed Ferlaino by phone to sell him to Maradona. “It drives me crazy. I called the Italian Federation to call UEFA, and the French Federation to calm Tapie down.” stated publicly the president of Naples. The second meeting was in Milan. Marseille went with everything. Maradona asked them the same salary as in Naples and Hidalgo promised that Tapie would give him double (€ 600,000 a month) and all his whims he asked for: a villa in an exclusive area, a garage for all his cars and even private security. Maradona looked strong and hesitated. “He threw the keys to the car at me and said” Will you come to get my Ferraris? “Tapie and I would have crawled on all fours if he had asked us to,” said Hidalgo in L’Equipe.With Maradona everything was fine but Ferlaino ended the story. “Maradona will stay in Naples as long as I want him to stay in Naples,” he said in this French newspaper, and Maradona never changed the ‘azzurro’ for the white and blue of the French team.Success for bothThe paths of Maradona and OM did not cross but both were successful. Diego won his second Scudetto with Napoli in 89/90 and Marseille became European champion in 93, before being relegated to the Second Division for arranging the pre-final match with Valenciennes so that they would not injure any player before the final. In 91, Maradona left Naples and in 95, Tapie left the OM, just when Diego returned to Boca. Diego Armando Maradona was able to leave Naples before 1991. In the late spring of 1989, Agent Michel Basilevich called the office of the recently deceased Michel Hidalgo, then sports director of Olympique de Marseille, to offer to sign 10. Hidalgo did not believe it, but the intermediary insisted and called Bernard Tapie, then owner of the Marseille, to tell him about it. Maradona, they assure, wanted to meet him.Tapie, a controversial character in France who has been a singer, actor, businessman, owner of Marseille and even a deputy and MEP associated with the left, was not encouraged. Basilevich bit him by calling L’Equipe to tell the whole story that this newspaper collects these days in chronological order.After a cover of this newspaper assuring that Maradona could land in Marseille, everything started. The first fear they had in Marseille, a city with a reputation for being dangerous, was the Neapolitan mafia. The good relationship between Maradona and Carmine Giuliano, a member of the Camorra, was known and that someone wanted to take Diego, who generated uncontrolled love between the Partenopeos, they believed that it could cause a rather difficult situation for them. Thus, confirmed his personal safety by an Italian contact that was never revealed, Hidalgo went to Italy with a premise: offer him whatever it was to Maradona.Negotiate with DiegoHidalgo arrived at Diego’s house ready to meet but on the 10th, according to L’Equipe, he had other chores and had the sports director waiting for hours while taking a photo session with his newborn daughter to sell it for solidarity purposes. “He came with us for about five minutes and left for an hour,” they say. When the session ended, they sat down to negotiate and Maradona was only interested in one thing: living well. “House, sea and pool, eh, Mr. Hidalgo?”, They assure that he answered. Maradona asked for player references and said he did not know any. Nor did he care. Naples loved him but he felt shut up. After the Camorra, the second fear of the people of Marseilles was Ferlaino, president of Nápoles and “owner of Maradona”. Diego assured that he would convince him to leave.
1. Client-side read-only cache: When app users simply need to read content while disconnected, client-side caching is the simplest wayto go. This allows the mobile app to bind the app’s user interface to a local data model and update the user interface when the local model changes. A great example of this type of offline support is Trane’s MAP app. The app, built by Cynergy (now part of KPMG), allows a salesperson to produce a quote for a customer while in the field. Pricing data updates at known intervals and the salesperson will not be updating it from their device. 2. Last write wins: ‘Last write wins’ is a better approach when offline app users need to add task creation, item updates or deletions in addition to reads. In cases where changes are infrequent and don’t come from multiple endpoints, robust conflict resolution policies aren’t critical. An example of this approach is an app that enables employees to update their internal social network, e.g., Chatter or Yammer. Submitting a status update is not dependent on previous updates to the server that may be overwritten. 3. Complete transactional synchronization: Follow this pattern when an app needs robust offline functionality while maintaining transactional integrity with back-end data stores or updates from different users or device channels. Building on the previous scenario, this allows for full mobile functionality along with fine-grained control of back-end conflict resolution. An example of this most comprehensive approach is an ERP approval process that must account for updates that may impact the approval justification while the mobile user is offline.Building a robust offline solution may be the most difficult development challenge in mobile, as mobile apps requiring network connectivity for baseline functionality limit a company’s brand appeal and growth. Most emerging markets, and many developed ones, have areas where cellular connections are constrained at best. Apps smoothly employing offline functionality will differentiate brands as showing concern and understanding for all customers, regardless of their network context. Parallel to the rise in importance of mobile apps comes increased emphasis on certain mobile platform services—geolocation, data service aggregation and home screen widgets, to name a few. Most of these are well understood by both consumers and developers, yet one sticks out as a challenge to both: offline access to app data. Business stakeholders almost always request support for offline usage scenarios at the beginning of a project, yet it is often nonexistent at the end. Why? The pain (and associated cost) of developing and testing the various facets of offline services causes this phenomenon. Yet offline services provide immense value to users; the ability to use the app absent network connectivity simply scratches the surface.Offline Support Comes In Three FlavorsNot every offline support requirement is identical. Some situations require a simple client-side cache of content to be browsed without a network connection, while others require a full store-and-forward transactional architecture. The unique flavors of offline are roughly differentiated by their support, or lack thereof, for back-end conflict resolution. Synchronization often introduces a scenario where a mobile device’s local version of a record is updated, but by the time the update is sent to the back-office service, the data there has also changed. This results in a conflict—which record should be used, the more recent server data or the incoming client data from a previous synchronization?Mobile developers can employ three common techniques for providing offline app support:
“[Atlassian cofounders] Mike [Cannon-Brookes] and Scott [Farquhar] had this philosophy that if you want to build something on this platform, here’s the source code: Go do it,” said Mancini. “Our ecosystem is founded in the concept of being open. I think that’s very unique.”That’s a distinctly different view from Apple, where the focus in on maintaining control of the app store at all costs, said Mancini.“I think the relationship with the development community is critical,” he said. “What we do to really differentiate ourselves is we make a point of being transparent with how we want to approve things. The challenge in other app stores is this aura of secrecy in order to protect against gamification. In an environment where there are hundreds of millions of dollars to at stake, people are going to want to game that.”Despite a marketplace crowded with app stores, Mancini said there is a plan that Atlassian follows in order to remain successful. “One of the challenges people have in creating open platforms is that you have to add value. Assisting in creation is great, and we all love the libraries and APIs. What really matters to developers is economic opportunity: having a foundation of customers and allowing them to fit into adding value for a core capability. The core capability for us is JIRA, Confluent, HipChat and BitBucket,” he said.To that end, Atlassian and its partners announced integrations at the Summit. Rollbar, a newcomer to the Atlassian world, introduced error detection software that can be plugged into an existing application. When an error or exception happens, Rollbar automatically logs and categorizes it. It also pushes through to the culprit code in the source-code-management system, allowing developers to quickly see when an error occurs and where it’s coming from.Other companies announcing integrations at the show included AppDynamics, Loggly, Puppet, Sauce Labs and dozens more. CircleCI introduced integrations with BitBucket, while SourceClear introduced the ability to scan BitBucket repositories for vulnerabilities. Atlassian continued its push to bring development teams together at the opening of its annual Summit in San Jose. Highlights from today included dozens of integration announcements from partners, as well as new features for BitBucket and other product lines.BitBucket now offers large file support and development pipelines, as both features were officially released out of beta at the show. The hosted source-code-management system also added two premium features: smart mirroring, and merge checking.Atlassian also extended the functionality of the Data Center editions of its core products. These include support for SAML 2.0, rolling upgrades with zero downtime, and the beta release of HipChat Data Center edition, which features support for larger instances and deployment of the collaborative chat program across multiple data centers.(Related: Atlassian updates BitBucket with pipelines)The biggest news at the show was that of momentum: Since its launch four years ago, the Atlassian marketplace has taken in more than US$200 million in revenue, and paid developers $150 million. Max Mancini, vice president of ecosystem at Atlassian, said that this growth has been accelerating.He said it took three years to reach the $100 million revenue mark, but only one year to reach the $200 million mark. He formerly headed up Apple’s e-commerce store, and as vice president of ecosystem, he is in position to see just what it is about Atlassian’s app store that makes it so successful.