This document discusses web hooks and the programmable world. It begins by explaining what web hooks are and why they are significant. It then discusses how web hooks enable a truly programmable web by allowing web applications and services to be extended and programmed, unlike existing APIs. The document covers examples of web hooks, comparisons to other technologies like REST and XMPP for push notifications, and argues that web hooks can cover most use cases by providing a simple lightweight alternative to push data. It envisions a future where web applications and services implement web hooks to allow different systems to integrate and work together through the pipes metaphor similar to Unix pipelines.
Memori utama merupakan media penyimpanan dalam bentuk array yang disusun word atau byte, kapasitas daya simpannya bisa jutaan susunan. Setiap word atau byte mempunyai alamat tersendiri. Data yang disimpan pada memori utama ini bersifat volatile, artinya data yang disimpan bersifat sementara dan dipertahankan oleh sumber-sumber listrik, apabila sumber listrik dimatikan maka datanya akan hilang.
Memori utama merupakan media penyimpanan dalam bentuk array yang disusun word atau byte, kapasitas daya simpannya bisa jutaan susunan. Setiap word atau byte mempunyai alamat tersendiri. Data yang disimpan pada memori utama ini bersifat volatile, artinya data yang disimpan bersifat sementara dan dipertahankan oleh sumber-sumber listrik, apabila sumber listrik dimatikan maka datanya akan hilang.
How to build and use GTPing to generate GTP traffic for testing without eNB, SPGW etc. This work was done as part of the preparation of SRv6 mobile user plane POC at SRv6 Consortium, Data plane Study Group, which is a group of people interested in SRv6.
All the content of this website is informative and non-commercial, does not imply a commitment to develop, launch or schedule delivery of any feature or functionality, should not rely on it in making decisions, incorporate or take it as a reference in a contract or academic matters. Likewise, the use, distribution and reproduction by any means, in whole or in part, without the authorization of the author and / or third-party copyright holders, as applicable, is prohibited.
This is a quick introduction to webhooks I gave at GlueCon 2010. It was also a bit of an ad for a last minute 40 minute talk I was giving immediately after.
An analysis of the trends in the web platform to help you plan, prepare and build for a better web. We'll go into ways to analyse trend data to help you learn more effectively about the platform, and we'll go into tools you'll need to make intelligent decisions when deciding on feature levels and browser support.
This presentation looks at various notions of “Web2-ness” within a wider context of a more wired web.
Although not the true “Semantic Web”, practitioners argue that many of the sites and services available today have the hallmarks of connectedness which Berners-Lee originally suggested would ultimately make up the next phase of the internet.
In the cultural context, this raises questions and outlines possibilities about how best to develop our web products so as to best capitalise on the notion that the power of the web is in sharing, and not – as has been typical to date - in silos.
The major issues tend to show themselves in two ways, and this presentation will focus on both: Firstly, how best to capture and share the voices of our users, and secondly how the power of the distributed web can help us cheaply and easily improve our offerings.
HTML5 is here and we should use it right now. It is fun and interesting to look at cool CSS3, Canvas and Video demos but our main goal should be to make our day-to-day life easier by using the cool things browsers offer us right now. Learn about local storage, simplifying interfaces and using HTML5 right now!
I broke what? Taking over maintenance on existing (well loved) projects, by B...T. Kim Nguyen
Taking over maintenance of an existing open source application can be a scary prospect yet exciting and fun at the same time. I want to talk a little bit about how I ended up taking over maintenance of WebOb a Python HTTP request/response library that is used heavily by a huge variety of projects.
Length: Long Talk
Target Level: Beginner
Target Audience: Integrator, User, Developer
How to build and use GTPing to generate GTP traffic for testing without eNB, SPGW etc. This work was done as part of the preparation of SRv6 mobile user plane POC at SRv6 Consortium, Data plane Study Group, which is a group of people interested in SRv6.
All the content of this website is informative and non-commercial, does not imply a commitment to develop, launch or schedule delivery of any feature or functionality, should not rely on it in making decisions, incorporate or take it as a reference in a contract or academic matters. Likewise, the use, distribution and reproduction by any means, in whole or in part, without the authorization of the author and / or third-party copyright holders, as applicable, is prohibited.
This is a quick introduction to webhooks I gave at GlueCon 2010. It was also a bit of an ad for a last minute 40 minute talk I was giving immediately after.
An analysis of the trends in the web platform to help you plan, prepare and build for a better web. We'll go into ways to analyse trend data to help you learn more effectively about the platform, and we'll go into tools you'll need to make intelligent decisions when deciding on feature levels and browser support.
This presentation looks at various notions of “Web2-ness” within a wider context of a more wired web.
Although not the true “Semantic Web”, practitioners argue that many of the sites and services available today have the hallmarks of connectedness which Berners-Lee originally suggested would ultimately make up the next phase of the internet.
In the cultural context, this raises questions and outlines possibilities about how best to develop our web products so as to best capitalise on the notion that the power of the web is in sharing, and not – as has been typical to date - in silos.
The major issues tend to show themselves in two ways, and this presentation will focus on both: Firstly, how best to capture and share the voices of our users, and secondly how the power of the distributed web can help us cheaply and easily improve our offerings.
HTML5 is here and we should use it right now. It is fun and interesting to look at cool CSS3, Canvas and Video demos but our main goal should be to make our day-to-day life easier by using the cool things browsers offer us right now. Learn about local storage, simplifying interfaces and using HTML5 right now!
I broke what? Taking over maintenance on existing (well loved) projects, by B...T. Kim Nguyen
Taking over maintenance of an existing open source application can be a scary prospect yet exciting and fun at the same time. I want to talk a little bit about how I ended up taking over maintenance of WebOb a Python HTTP request/response library that is used heavily by a huge variety of projects.
Length: Long Talk
Target Level: Beginner
Target Audience: Integrator, User, Developer
Rich, modern web-applications are changing the way we write software for the Internet. As browsers grow evermore powerful, we become able to construct more complex and interactive applications by deferring some server-side logic to the client. In this presentation, we will establish a definition and characteristics for what makes web-applications modern and compare the benefits and trade-offs by exploring a few case studies.
About the Author:
Mike Filbin is a full-stack web developer who focuses on engineering JavaScript applications for both the browser and the server. Mike is also a proponent of the Free and Open Source software movements and is a member of both the Linux and Free Software foundations.
Session slides from Future Insights Live, Vegas 2015:
https://futureinsightslive.com/las-vegas-2015/
Modular front-end applications that can grow and evolve over time. Many front-end JS toolkits are optimized for building the first version of the app quickly. But for an app that powers a business, you have to think past initial launch. Your app will likely outlive the attention span of those who first wrote it. So, how do we pick tools and architectures that can be modified, maintained, and upgraded over time by a team of people?
An exploration of the cultural lineage where Hacker Dojo came from, including SHDH, LGLAN, and how Dojo is memetically related to BarCamp and Coworking.
Beyond Mashups: Service Integration and MoreJeff Lindsay
This is the intro deck I used to frame my standard talk on web hooks around mashups. After these slides, continue with <a href="http://www.slideshare.net/progrium/web-hooks-and-the-programmable-world-of-tomorrow-presentation">this slideshow</a>
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
1. WEB HOOKS
and the
Programmable World of Tomorrow
Jeff Lindsay
three years after coining web hooks, people are starting to get excited about them.
i’m going to share what they are, why they’re significant, and what’s going on
in the growing web hooks ecosystem
2. WEB HOOKS
and the
Programmable World of Tomorrow
Jeff Lindsay
i’ve given a version of this talk before, but this time i’d like to try and focus on this
“programmable” idea that helped inspire web hooks.
3. WARNING:
Emergent dynamics described ahead.
was a guy really excited hearing about web hooks, but was disappointed to see what they are.
i’m describing a game changer based on a mechanism that takes one line of code to describe.
seems so simple, people assume you can only do simple things. quite the contrary...
4. go. simple mechanisms can create rich dynamics.
easily teach somebody the rules, doesn’t mean they see the implications of those rules.
i want to share the implications of this simple mechanism.
5. in 1997, jon udell talks about websites as data sources that can be reused and remixed
today that idea isn’t very novel
6. “a new programming paradigm
that takes the whole Internet
as its platform”
he envisions the Internet as a programming paradigm
7. The Programmable Web
“The Web as Platform”
it starts to manifest as the programmable web and talk of “the web as a platform”
8. The Programmable Web
APIs and Mashups
john musser here starts to track apis and mashups in 2005. there are now over 1k apis and
increasingly more.
apis and mashups became the foundation of the programmable web...
9. Pro g ramm at ic
The Programmable Web
APIs and Mashups
but are they? after thinking about web hooks and what they can give us, i realized apis and mashups
don’t make a programmable web. they make a programmatic web
10. Pro g ramm at ic
The Programmable Web
Twitter API lets you use Twitter programmatically.
It does not let you program Twitter to do more.
they let you use web apps programmatically. they don’t let you program them to do more,
whereas web hooks can. so i like to argue that web hooks will bring about the *real* programmable
web.
11. Web Service
interwebz
User
so let’s get specific. here’s an example scenario showing the use of web hooks.
12. Web Service
Hi, I’m Twickr,
a new web service.
interwebz
User
22. “Twickr”
It doesn’t matter to you.
Whatever I want...
interwebz
User
web hooks are just user-defined http callbacks
23. Web Service
EXTENSIBLE
interwebz
EMPOWERED
User
but do you see what they did? they made the web service extensible and empowered the
user.
24. a friend of mine got me to explain web hooks to her. not a programmer, but has iphone.
she compared it to jailbreaking the iphone: letting users do what they want, customize, add
apps, etc
having web hooks is like jailbreaking your web apps. opens functional extensibility.
25. a pseudo code example of what the heart of implementing web hooks looks like.
SIMPLE: make an HTTP request to a user-specified URL on major events
28. “When a customer pays you, PayPal posts a notification to your server at a URL you specify.”
its framed as a notification, but that doesn’t properly imply the usage its intended for:
integration.
29. started thinking about this in 2006.
everything flashed before my eyes and was very confused why it wasn’t used more.
felt like i was taking crazy pills. today i know why...
31. both have been around longer. rest is simpler..
in fact, it’s almost described as “using HTTP properly”
but not until it got a name could it be used in discourse to make it popular
32. REST
Hooks
rest apis and web hooks are two sides of the same coin
they complement each other in ways i’ll get to later
but i just want to give this pattern a name, and start associating some ideas with it
33. Push
Pipes
Plugins
talk is split into three sections
ways to look at the use of web hooks
icons will hopefully make more sense as i talk about them
34. Push
let’s get started with push
people are starting to talk about push and pubsub on the web... although its not the first
time
35. 1998 (predating rss) microsoft submitted an internet draft to extend http
to provide a basic pubsub framework called GENA
40. but then in 2000, rss 0.92 was released. five years later it gets an icon and widespread
adoption.
it started with blog feeds, then comment feeds...
41. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
42. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
43. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
44. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
45. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
46. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
47. then soon exploded into twitter feeds, photo feeds, activity feeds, event feeds, bookmark feeds
even feeds of feeds
48. it makes you think of feeds like in the telecom world
52. then it gives it to us. and we do this over and over.
are we there yet? are we there yet?
53. ?
feeds made sense in a world where feed readers ran on
desktops that couldn’t be pushed to over http
54. ?
of course, now we have other web applications consuming feeds and it doesn’t make sense.
even most of our feed readers have become web applications
55. SUP is a recent incremental solution to increase the eficiency of consuming large amounts of
feeds.
however, its based on polling and is essentially yet another feed,
so i couldn’t help...
56. SUP DAWG, WE HEARD YOU LIKE FEEDS
SO WE MADE YOU A FEED OF OUR FEEDS
57. evan and kellan gave a great talk a while back about this push issue, and their proposed solution:
xmpp
i have a condensed version of this talk. the slides speak for themselves
58.
59.
60.
61.
62.
63.
64. (aka XMPP)
they have a great point. polling sucks, and xmpp is a pretty good solution for data streams
65. but it’s kind of heavy weight. it does a lot and makes a decently complex little system.
luckily it’s not *that* hard to use with today’s library support
66. evan and kellan did point out there are extremes when it comes to data streams.
most data streams will probably fall somewhere in between,
but i do think xmpp is suited for the fast and furious end
67. joshua schachter of delicious responded to this talk in a blog post.
he basically suggests web hooks as an alternative
68. “One solution that occurred to me at the time was to build a simple callback system over HTTP.
This would fall comfortably between full polling and full persistent publish/subscribe.”
he says they fall comfortably between polling and xmpp. i agree, and think they can cover
most use-cases
69. others seem to agree....
this is a standard for discovering and subscribing to content changes.
they let you use web hooks OR xmpp, which is nice.
good idea, but (like GENA) standard specs alone don’t get very far
70. gnip is a service that some may have heard of (but don’t understand)
72. Source Destination
Protocol + Mechanism Protocol + Mechanism
Format Format
Web Hooks Web Hooks
RSS RSS
XMPP XMPP
Atom Atom
XML XML
REST REST
Publisher Consumer
they’re basically an adaptor for data streams, letting you pick your own protocol and mechanism, no
matter what the feed publisher is providing.
73. Source Destination
Protocol + Mechanism Protocol + Mechanism
Format Format
Web Hooks Web Hooks
RSS RSS
XMPP XMPP
Atom Atom
XML XML
REST REST
Publisher Consumer
however, they recently dropped support to consume via xmpp, making web hooks their primary push
mechanism for consuming data streams.
74. Source
Protocol + Mechanism Protocol + Mechanism
Format Format
Web Hooks Web Hooks
RSS RSS
XMPP XMPP
Atom Atom
XML XML
REST REST
Publisher Consumer
as an example, if i wanted to get digg updates via web hooks, gnip will poll digg for me and invoke my
callback with the content as new updates come in.
75. Source
Protocol + Mechanism Protocol + Mechanism
Format Format
Web Hooks Web Hooks
RSS RSS
XMPP XMPP
Atom Atom
XML XML
REST REST
Publisher Consumer
alternatively, i could even poll gnip for digg updates. although seemingly redundant, it helps ease the
load on digg and allows gnip to provide filtering functionality.
76. Protocol + Mechanism Protocol + Mechanism
Format Format
Web Hooks Web Hooks
RSS RSS
XMPP XMPP
Atom Atom
XML XML
REST REST
Publisher Consumer
but another example might be if twitter provides an xmpp stream, but i already have a polling setup...
gnip would let me poll instead of integrate xmpp.
77. microformats
in promoting web hooks, i sort of look up to the way microformats work in values and process.
very ground up, grassroots... take existing popular use-patterns and make it a convention.
microformats can be viewed as an alternative xml+rdf
78. xml+rdf vs microformats
“Here's a new language we want you to learn,
and now you need to output these additional
files on your server. It's a hassle.
(Microformats) lower the barrier to entry.”
tantek is a big microformats evangelist. he says....
so i told him about web hooks. “what are they?” “push over http”
“how are they di than xmpp?” “they’re a lightweight alternative” lower the barrier to entry...
79. xmpp vs web hooks
“Good. XMPP needs a competitor.”
he says...
this was encouraging. i mean, when tantek talks, you listen...
if for no other reason than
81. unfortunately, xmpp has many features and proposals to do pubsub that web hooks doesn’t.... after
all, it’s just a creative use of http requests, not a messaging protocol. so in order to do pubsub with
web hooks, you need more to be implemented. well, brad fitzpatrick and brett slatkin are working on
that.
82. Push is good.
so the moral here is that push is good and there’s finally a demand for it. we have some good
solutions waiting adoption...
83. XMPP is ideal when needed,
but Web Hooks generally do the job.
as far as xmpp vs web hooks, i think they both have their place.
web hooks are easier, so you might as well default to web hooks unless you really need
xmpp.
84. But push is not the point.
however, as i framed this talk, it’s really not about push. it’s a nice way to get the social
media kids into bed with web hooks, but hooks are really about more than pubsub and
notifications. otherwise i would have called them web notifications or something...
85. Pipes
instead of push, i was more drawn by the pipes metaphor. i wanted to integrate and
orchestrate the web applications i use, conceptually similar to unix pipelining.
86. so i thought about it. pipes were a really amazing feature that let you get more out of your commands
by letting you chain them together. it sort of let you program without programming, combining
commands in ways that weren’t necessarily intended by the author.
87. Input Output
Program
all from a bit of infrastructure involving input and output
88. STDIN STDOUT
Program
STDERR
stdin, stdout were available to reroute wherever the user wanted
most common use was chaining commands together: piping
89. xargs
wget
echo
mail
grep
wc
cat
so you had all these simple little programs, that might not even be useful alone
90. cat
xargs
wget
echo
mail
grep
wc
string them together...
92. cat grep mail
xargs
wget
echo
wc
and you have something more useful than the sum of the parts
93. Write programs that do one thing and do it well.
Write programs to work together.
Write programs that handle text streams,
because that is a universal interface.
this helped put forth the unix philosophy and encouraged building these small composable
commands
94. STDIN
Program
but it doesn’t work without the output. it just breaks.
95. API
Web App
unfortunately that’s how the web is today.
we can talk to web apps, but they really can’t talk to us. or anything else really.
96. API Hooks
Web App
it’s not that they can’t, they just don’t. we just need to start putting hooks in so they can.
those roles are best played by mechanisms that use the protocol the web is built on: http
99. cat grep mail
Basecamp
so we want to combine web applications like we can CLI programs.
get more than the sum of the parts.
web hooks open up this possibility, but need like APIs, need to be implemented
101. Basecamp
Project finished
Todo completed
Milestone created
Contact added
File uploaded
102. Basecamp
My handler
http://example.com/handler
users can write handlers that are just web scripts.
they have a url, and thats what you give basecamp
103. Basecamp
My handler
http://example.com/handler
it’s code. it can do anything from there.
integrate with other services, make a phone call, order pizza, whatever
104. Todos
Basecamp
for example, all these apps share data about todos. they each have respective specialized talents,
but all work with todos. by putting hooks on todo CRUD,
you can use their apis to keep them synced pretty well. magically. real-time.
107. Code as glue
based on the idea that web urls can run code. and code can do anything.
108. when i first thought about this, cheap PHP hosting was all over, but it could be even simpler.
there are paste bins like this one. made to share formatted code with people over IRC or email
109. put in some code you want to share or ask a question about
113. Basecamp
Project finished
http://pastie.org/run/24576
for example, basecamp. now when you finish a project, everybody meets for shots in the break room.
115. just hit a button, write code, hit save, share the url. it’s javascript
116. obviously app engine, although it’s a little more involved than appjet for quick handlers.
but it is an option for python.
and there are ruby/rails hosts like heroku
117. one thing i’ve been working on is an extension to play with ways end-users might interact
with web hooks
118. Hey, there’s an
event hook here!
by detecting some markup in a page, it discovers hooks.
like say for new photos from contacts.
you want to do something when that happens, click it
119. Save
and write some code. hit save, it posts to AppJet (or wherever),
registers the handler (assuming a standard protocol), and done. all inline.
go back and change the code.
120. Real world examples
but these are all mockups and what-ifs...
there is a world of web hooks already evolving...
121. i started by exposing svn hooks as web hooks in devjavu
122. i talked about web hooks enough using pbwiki as an example,
their mysterious cto decided to implement them
124. went all out on hooked events. not sure if it’s made it to production, but really cool
125. “Building projects with web hooks in
mind lets me keep the core Lighthouse
source focused, while external
services live in their own libraries.”
--Rick Olson
the idea silently spread to rails guys.
rick olson used them in lighthouse
126. “We implemented web hooks a while
ago and people have been building all
sorts of unexpected stuff on top of it.”
--Tobias Lütke
tobias used them in shopify. i’m told he’s revamping their api to have more hooks. they were
one of the earliest adopters and recently had their 1 yr anniversary using web hooks
127. google code recently caught up other code hosts by providing a post commit hook.
it was very well done, as you’d expect from google and in particular shows that
authentication can be done with hmac signatures
128. github was one of the first majorly popular site to use and promote web hooks.
129. they’ve been doing really well with their post-receive hook. users have used it to integrate
with mailing lists, chat, other project management tools, continuous integration, etc
130. they were so successful with the adhoc integration, they formalized it.
but in the best way! using their existing web hook infrastructure.
they just have modules running in a separate but local web service.
131. in fact, that lets them open source it. letting people fork, write new handlers, and push back.
this is probably going to be the standard model of service integration.
132. and a great example of services integrated with github, besides lighthouse, is runcoderun.
they run your regression tests for you. continuous integration in the sky. love it.
they sign you up automatically if you put their hook in github.
133. and of course i mentioned paypal. but i should mention, web hooks make so much sense
for paypal... they’re not so much about pushing content, but INTEGRATING. that’s what
web hooks are great for, even though they can be used for content push.
134. jott is another example of a web hook implementer that doesn’t know it.
they parse voice over the phone and do stu with it, like post to twitter, etc
135. they do it with “Links”... which are just hooks. they post to a script that does something with
the parsed text. really cool for todos.
136. Jott reads back the
The message is Message is sent via User receives
User jotts to
response and sends
converted HTTP Post to a information back
a Jott Link
it via SMS SMTP
into text web page
here’s their diagram. totally web hooks.
137. it become obvious making adaptor services would not only be useful in specific cases, but in
general, it makes sense to have services that will turn other protocols into inputs to the web
hook ecosystem. the first was email... i built mailhook...
138. GAE community made one because GAE doesn’t have a way to accept email (but will soon).
web hooks were the obvious solution.
139. rick olson has an open source non-hosted ruby version that will do xmpp.
he uses it for lighthouse.
140. but smtp2web is interesting because it was made because of the limitations of GAE...
141. in fact a lot of people made these kinds of “micro webservices” to do simple things GAE
didn’t do. it was the first glimpse at small, focused services that are like the equivalent of
grep, cat, wordcount, etc in the command line piping ecosystem.
142. then there’s martyn and andy. two guys in the uk that love web hooks.
they built this thing called spaghetti junction at a hackday. it involved into...
143. switchub. i REALLY love this. i knew this sort of thing would emerge, but i didn’t think it would happen
until web hooks were more popular. kind of like the pastinbin code runner, they let you create hook
inputs with urls to put in apps that you can route to various output handlers: email, irc, etc
144. my example switchboard. this kind of feels like gnip, only more focused and more about web hooks.
so i like it lots.
145. opening handlers up like github. anybody can write handlers soon.
working with them a little to make it real awesome.
146. switchub would benefit from builtin inputs from various other protocols like email, rss, etc...
but instead of having them builtin, they can work with other services to support those kinds
of inputs. for example, rssfwd could easily be modified to provide a web hook for rss
147. switchub is a lot like how i visualized a way for regular users to orchestrate web apps.
was inspired by reason: virtual rack mounts
148. flip it around and wire them together however you like. totally cool.
153. tangent: this is a neat find. was on reddit. andreessen proposing IMG tag.
people fought it, said it needed to be more generalized.
he just put it on mosaic and that was that
162. Extend
Integrate
Function
Content
but extending apps...
163. almost called this section Platforms.
platforms are really cool. we all love them.
i LOVE them, so fb platform was really cool.
asked a friend how it worked. he said “web hooks”
164. sure enough, this looks like web hooks to me. as long as it’s http, calling out... but then using the
results in their app? thats dierent...
165. in fact a few people have used web hooks for plugins. dabble is a great example.
166. they do online databased for people that use excel as a database.
168. “Dabble plugins allow Dabble applications to create new, derived fields by calling out
to external HTTP-accessible applications. This solves the problem of safely enabling
extension of a centrally-located hosted application, in that, while you’re writing code
to extend and enhance the behavior of a Dabble application, your code never
actually runs inside Dabble.”
[General]
Name = Amazon Sales Rank
[Sales Rank by ISBN]
URL = http://chadfowler.com/dabble/amazon_sales_rank.cgi
Input = Text
Output = Number
only they have an extra layer for meta data. but that’s a cool pattern.
169. “If you’ve used a UNIX-based operating system, you’re probably
familiar with the notion of pipes. The output of one program is
piped into the input of another, creating a filter chain. This is
conceptually the same as the way Dabble’s plugin IO works.
Nice and simple.”
of course, they compare it to pipes. the simplicity. the natural fit of it.
170. of course, i think they should have web hooks for all their standard CRUD events...
this way their database apps can integrate (like PayPal) with the rest of your workflow
171. in fact, all these “app platforms” like coghead and salesforce should have web hooks.
that would make them more useful, less silo’d o into just processing data in their world
172.
173.
174. IMified uses web hooks. sells the tech too: “allows anyone with basic web programming skills
to quickly and easily create ...”
176. General Systems
Theory
central tenet is value is not in the elements or parts of a system
177. General Systems
Theory
the real value is in the interactions, how they work together.
this creates the emergent phenomenon of a system, and defines its behavior
180. “a new programming paradigm
that takes the whole Internet
as its platform”
this vision for a programming paradigm that IS the internet/web is very compelling... but we’re not
there yet.
184. “What is the equivalent of the pipe
in the age of the web?”
in 2000, just as rss 0.92 was being released, tim oreilly asks...
since we had nothing better, we assumed the answer was feeds.
185. this eventually gave us yahoo pipes. which just didn’t seem to change the game like you would think...
perhaps feeds just aren’t the answer. or maybe they are and the problem is using the pipes analogy.
it’s definitely a stretch...