The Evented Web Makes Users Happy
1 like819 views
Events will change how we use the Web and make people happier. Promise.
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #10: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #11: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #12: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #13: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #14: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #15: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #16: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #17: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #18: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #19: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #20: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- #21: The most important feature for this discussion is that each Web site is a silo. The location metaphor works fine when what you want to do is confined to that silo. But what happens when you need information from multiple places to accomplish your task?\n
- #22: \n
- #23: \n
- #24: \n
- #25: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #26: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #27: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #28: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #29: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #30: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #31: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #32: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #33: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #34: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #35: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #36: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #37: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #38: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #39: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #40: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #41: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #42: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: complex event processing not unusual in the enterprise\njust developing on the more general Web\nidentity\nloosely coupled system\n
- #54: \n
- #55: KRL: \n- rule based\n- sophisticated event expressions\n- in cloud\n- API ready\n
- #56: No one’s ever surprised me with a GUI\nIndirection allows us to fix problems once\nLanguages are how programmers encapsulate problems and create abstractions\n
- #57: Abstraction layer\nMental model\n
- #58: \n
- #59: when you folloiw someone on twitter, you are creating a static query against the river of tweets\nwe’ve create a rule language, KRL, to work in this new model. \n
- #60: \n
- #61: \n
- #62: call out the abstract in this expression\n
- #63: we’ve already seen KRL rules employed in applications that increase customer satisfaction and make online interactions more convenient\n\n
- #64: patient doctor connections are more effective\n
- #65: parents create more play opportunities for their children\n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n
- #71: Turn by turn directions are a good example of notifications providing value.\n