How does the Web work?
•
1 like•362 views
The document discusses how the web works using HTTP and REST principles. It explains that resources on the web are identified by URIs and can be documents, concepts, or ideas. It describes HTTP verbs like GET, POST, PUT, and DELETE and how they differ in whether they are idempotent or cause side effects. It also discusses how Rails implements RESTful services and the differences between AJAX and traditional page loads.
Report
Share
Report
Share
Download to read offline
Recommended
Services in Drupal 8
This document discusses services and REST APIs in Drupal 8. It defines key concepts like web services, REST, and the Richardson Maturity model. It explains the components of a REST request and how requests work. Drupal 8 introduces a new routing system based on Symfony, and resources are exposed via plugins that define routes for CRUD operations. Serialization and normalization convert entities to JSON/HAL. Authentication is decoupled from sessions. Overall the document provides an overview of the RESTful services architecture in Drupal 8.
RESTful Web Services and Drupal
The document discusses Representational State Transfer (REST) and RESTful web services. It explains some key REST concepts like resources, URIs, HTTP methods, and statelessness. Resources are any information that can be named and accessed over the web, and each resource has a unique URI. HTTP is a stateless protocol where each request is independent. The document also covers how resources link to each other through hyperlinks and embedding URIs.
REST vs SOAP
REST and SOAP are two main web service architectures. REST uses standard HTTP methods like GET, POST, PUT, and DELETE to perform operations on resources identified by a URI. Data is usually represented in XML or JSON. SOAP always uses POST and defines operations as methods identified by a URL. The SOAP request includes an XML envelope containing the method call and parameters. REST is simpler, more flexible and secure than SOAP making it the preferred choice for web services.
Building Awesome APIs with Lumen
An overview of how to structure your Lumen APIs to make them awesome. Topics covered: requests, responses, logging, documentation and testing.
Slides assume some background in Laravel.
Browsers_SameOriginPolicy_CORS_ContentSecurityPolicy
This document discusses cross-origin resource sharing (CORS) and content security policy (CSP) as techniques to improve security in web applications. It begins by explaining the need for the same-origin policy and how CORS helps address limitations of SOP by allowing controlled cross-origin requests. It then discusses cross-site scripting (XSS) attacks and how CSP helps prevent XSS by allowing web applications to restrict resources that can be loaded or executed.
Same origin policy
The document discusses techniques for making cross-origin requests, including JSONP, CORS, and using Document.domain. JSONP works by dynamically inserting a <script> tag to load data via a JSON callback. CORS uses special request and response headers to allow cross-origin requests. Document.domain can make pages across different ports appear to be the same origin.
Xitrum internals
Xitrum uses the Netty framework and follows a handler-based architecture. It aggregates HTTP requests and responses into a HandlerEnv object that passes through various handlers. These handlers include converting requests to HandlerEnv, selecting and calling actions, converting responses back to HTTP, and more. Routing is done by collecting routes specified by annotations at startup and dispatching requests to the appropriate action class execute method.
RESTful web services
The document discusses REST (Representational State Transfer) and HTTP best practices. It covers REST constraints like resources having identifiers and a uniform interface using HTTP methods. It provides examples of using a collection resource with GET to retrieve a list of items and a specific item, and POST, PUT, and DELETE to create, update and delete resources. It also briefly mentions advanced topics like link relations, AtomPub, reliability, and asynchronous patterns.
Recommended
Services in Drupal 8
This document discusses services and REST APIs in Drupal 8. It defines key concepts like web services, REST, and the Richardson Maturity model. It explains the components of a REST request and how requests work. Drupal 8 introduces a new routing system based on Symfony, and resources are exposed via plugins that define routes for CRUD operations. Serialization and normalization convert entities to JSON/HAL. Authentication is decoupled from sessions. Overall the document provides an overview of the RESTful services architecture in Drupal 8.
RESTful Web Services and Drupal
The document discusses Representational State Transfer (REST) and RESTful web services. It explains some key REST concepts like resources, URIs, HTTP methods, and statelessness. Resources are any information that can be named and accessed over the web, and each resource has a unique URI. HTTP is a stateless protocol where each request is independent. The document also covers how resources link to each other through hyperlinks and embedding URIs.
REST vs SOAP
REST and SOAP are two main web service architectures. REST uses standard HTTP methods like GET, POST, PUT, and DELETE to perform operations on resources identified by a URI. Data is usually represented in XML or JSON. SOAP always uses POST and defines operations as methods identified by a URL. The SOAP request includes an XML envelope containing the method call and parameters. REST is simpler, more flexible and secure than SOAP making it the preferred choice for web services.
Building Awesome APIs with Lumen
An overview of how to structure your Lumen APIs to make them awesome. Topics covered: requests, responses, logging, documentation and testing.
Slides assume some background in Laravel.
Browsers_SameOriginPolicy_CORS_ContentSecurityPolicy
This document discusses cross-origin resource sharing (CORS) and content security policy (CSP) as techniques to improve security in web applications. It begins by explaining the need for the same-origin policy and how CORS helps address limitations of SOP by allowing controlled cross-origin requests. It then discusses cross-site scripting (XSS) attacks and how CSP helps prevent XSS by allowing web applications to restrict resources that can be loaded or executed.
Same origin policy
The document discusses techniques for making cross-origin requests, including JSONP, CORS, and using Document.domain. JSONP works by dynamically inserting a <script> tag to load data via a JSON callback. CORS uses special request and response headers to allow cross-origin requests. Document.domain can make pages across different ports appear to be the same origin.
Xitrum internals
Xitrum uses the Netty framework and follows a handler-based architecture. It aggregates HTTP requests and responses into a HandlerEnv object that passes through various handlers. These handlers include converting requests to HandlerEnv, selecting and calling actions, converting responses back to HTTP, and more. Routing is done by collecting routes specified by annotations at startup and dispatching requests to the appropriate action class execute method.
RESTful web services
The document discusses REST (Representational State Transfer) and HTTP best practices. It covers REST constraints like resources having identifiers and a uniform interface using HTTP methods. It provides examples of using a collection resource with GET to retrieve a list of items and a specific item, and POST, PUT, and DELETE to create, update and delete resources. It also briefly mentions advanced topics like link relations, AtomPub, reliability, and asynchronous patterns.
REST API Laravel
This document provides an overview of RESTful APIs and how to build them using Laravel. It defines REST as an architectural style for designing networked applications that use HTTP to perform CRUD operations on resources. The key aspects of RESTful APIs covered include using HTTP verbs like GET, POST, PUT and DELETE; including HTTP headers and status codes; being stateless; and commonly returning JSON or XML responses. The document also discusses authentication methods like OAuth and JSON web tokens that can be used to secure REST APIs. Finally, it outlines the steps that will be covered to build a RESTful API using Laravel, including creating routes, migrations, seeders, models, controllers and request validation.
Creating Restful Web Services with restish
This document discusses creating RESTful web services using the restish framework. It provides an overview of REST principles like resources, representations, and the uniform interface. It also demonstrates building a simple TODO list management application with restish and discusses testing and deploying restish applications.
Designing RESTful APIs
This document provides an introduction to designing RESTful APIs. It discusses HTTP, REST architectural principles, and how to design APIs around resources and use HTTP methods and status codes. Examples of good and bad RESTful APIs are provided, along with exercises to design RESTful versions of existing APIs. Authentication patterns like API keys and OAuth are also covered.
Rest
This document summarizes a workshop on web services and the Richardson Maturity Model (RMM). It explains how a basic web service works by sending an XML request to a server, which decodes it and executes the specified function, then encodes and returns a response. It then describes the four levels of the RMM - from simple request/response using HTTP as a tunnel, to introducing resources at level 1, using HTTP verbs properly at level 2, and finally implementing HATEOAS at level 3 to provide link relations between resources. The document concludes by listing prerequisites for the workshop demo application.
REST library.pptx
The document discusses Representational State Transfer (REST), which is an architectural style for building web services. REST uses commonly used HTTP methods like GET, POST, PUT, PATCH, and DELETE to perform CRUD (create, read, update, delete) operations on resources. These requests use URLs to specify resources and return responses in formats like JSON or XML. The document provides examples of how each HTTP method maps to different CRUD operations and requests and responses using a sample student API.
REST and Web API
The document discusses REST (Representational State Transfer) and the Richardson Maturity Model for building RESTful web APIs. It explains the four levels of the maturity model - from simple request-response (Level 0) to full REST with hypermedia links (Level 3). It then provides an overview of how to build RESTful services with the ASP.NET Web API framework, covering routing, controllers, OData support, and extensibility options.
REST and Web API
The document discusses REST (Representational State Transfer) and the Richardson Maturity Model for building RESTful web APIs. It explains the four levels of the maturity model - from simple request-response (Level 0) to full REST with hypermedia links (Level 3). It also provides an overview of how to build RESTful services with ASP.NET Web API, including URL routing, content negotiation, and extensibility options like message handlers and dependency injection.
HTTPs Strict Transport Security
This document discusses HTTP and HTTPS protocols. It provides information on web servers, HTTP requests and responses, status codes, headers, methods, and SSL/TLS encryption. The key points are:
- HTTP is an application layer protocol for distributed, collaborative hypermedia information systems. It uses a request-response protocol to transfer data between clients and servers.
- HTTP requests consist of a start line with method, URI and version, followed by headers and an optional message body. Common methods are GET, POST, PUT, DELETE.
- HTTP responses contain a start line with status code and reason, followed by headers and an optional message body. Status codes indicate success, redirection, client or server errors.
WebApp #3 : API
The document provides an overview of REST APIs and how they can be used to build web applications. It discusses HTTP and URLs, defines REST and its architectural constraints, and shows how to implement REST principles using HTTP methods, URLs and response codes. The document also covers REST API design best practices like versioning, limiting fields, using JSON format, and handling errors properly. It provides resources for further reading on REST APIs and their implementation.
Why do you need REST
This document discusses REST vs SOAP and recommends ASP.NET Web API for building RESTful services. It explains that REST focuses on resources and HTTP verbs while SOAP defines custom operations. REST uses the existing features of the web like caching and scalability. The document provides examples of SOAP and REST requests and responses. It recommends ASP.NET Web API for building REST services and WCF for SOAP.
HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs
The document provides an overview of the history and evolution of HTTP protocols, from versions 0.9 to 3. It discusses key aspects of HTTP/1.1 including resources, client-server architecture, status codes, and REST. HTTP/2 improvements like multiplexing and binary format are covered. Emerging technologies like GRPC, RSocket, and HTTP/3 which uses QUIC are also summarized. The future of application programming interfaces and network communication is moving towards lower latency protocols built on top of HTTP like HTTP/3 that leverage UDP.
Building Restful Applications Using Php
This document summarizes a presentation about building RESTful applications using PHP. REST (Representational State Transfer) is a software architectural style that uses HTTP verbs to manipulate resources. The presentation covers the six constraints that define REST - client-server separation, statelessness, cacheability, uniform interface, layered system, and code on demand. It provides tips for implementing REST in PHP like using the header() function, determining the request method, and encoding/decoding JSON. Questions from the audience are answered at the end.
REST in ( a mobile ) peace @ WHYMCA 05-21-2011
RESTful architectures and the advantage for HTTP consumers.
Focused on what matters to the mobile world: performances & scalability.
An Introduction To REST API
This document provides an introduction and overview of REST APIs. It defines REST as an architectural style based on web standards like HTTP that defines resources that are accessed via common operations like GET, PUT, POST, and DELETE. It outlines best practices for REST API design, including using nouns in URIs, plural resource names, GET for retrieval only, HTTP status codes, and versioning. It also covers concepts like filtering, sorting, paging, and common queries.
Fulfilling the Hypermedia Constraint via HTTP OPTIONS, The HTTP Vocabulary In...
This document summarizes a presentation on fulfilling the hypermedia constraint in RESTful systems using HTTP OPTIONS requests, representing HTTP requests and responses in RDF, and using link headers. It discusses modeling API specifications and constraints using these techniques to transparently provide documentation and controls to user agents. Examples are given of annotating YouTube video IDs requested from an API with RDF and using link headers to indicate related resources.
Anintroductiontojavawebtechnology 090324184240-phpapp01
This document provides an introduction to Java servlets and web technologies. It discusses HTTP protocols and methods like GET and POST. It explains concepts like web containers, servlet lifecycles, and the structure of web applications. It also provides instructions for setting up a servlet development environment with Java, Tomcat, and configuring the CLASSPATH variable. Finally, it outlines some important servlet API classes and interfaces.
Restful web services
This presentation covers basics of RESTful webservices. I have prepared it by reading different online tutorials. One of them is java brains video tutorial. Hope this helps some one.
If any one needs examples mentioned in the slides, please contact me.
Web Tech Java Servlet Update1
The document provides an introduction to Java web technology and servlets. It discusses HTTP and its request/response model. It describes common HTTP methods like GET and POST, and explains the difference between the two. It also covers the servlet lifecycle, web containers, and setting up a servlet development environment.
HTTP: the Other ESB
Presented at Houston Tech Fest 2009.
Many developers use enterprise service bus (ESB) tools such as BizTalk or, for those looking at a lighter-weight approach, NServiceBus. What many fail to realize is that we have another option, one that has been tried and tested for many years and that we all use daily: HTTP. Find out how HTTP can deliver a much more maintainable, simpler solution to your ESB problems.
An Introduction To Java Web Technology
This document provides an introduction to Java web technology and servlets. It discusses HTTP and its request/response model, HTTP methods like GET and POST, the servlet lifecycle including initialization, request handling, and destruction, and the basic structure of a web application. It also provides an overview of setting up a servlet development environment with Java, Tomcat, and configuring the CLASSPATH.
Where Does the Fat Goes? Utilizando Form Objects Para Simplificar seu Código
The document discusses using form objects to simplify code in monolithic applications. It describes problems with "fat controller" code that handles many responsibilities in a single controller action. This can lead to divergent changes, feature envy, and inappropriate intimacy code smells. The document proposes refactoring code using principles like "slim controller, fat model" - moving logic from controllers to models using form objects. This improves separation of concerns and adherence to rules like short methods and single responsibility classes.
Descobrindo APIs REST
Este documento fornece uma introdução sobre APIs REST, definindo o que é REST e hipermídia, discutindo como projetar e implementar uma API REST passo a passo e mencionando algumas ferramentas e bibliotecas úteis. O documento explica como entender o fluxo de trabalho da API, construir uma máquina de estados, criar tipos de mídia e implementar a API usando exemplos de pedidos e pagamentos em uma lanchonete.
More Related Content
Similar to How does the Web work?
REST API Laravel
This document provides an overview of RESTful APIs and how to build them using Laravel. It defines REST as an architectural style for designing networked applications that use HTTP to perform CRUD operations on resources. The key aspects of RESTful APIs covered include using HTTP verbs like GET, POST, PUT and DELETE; including HTTP headers and status codes; being stateless; and commonly returning JSON or XML responses. The document also discusses authentication methods like OAuth and JSON web tokens that can be used to secure REST APIs. Finally, it outlines the steps that will be covered to build a RESTful API using Laravel, including creating routes, migrations, seeders, models, controllers and request validation.
Creating Restful Web Services with restish
This document discusses creating RESTful web services using the restish framework. It provides an overview of REST principles like resources, representations, and the uniform interface. It also demonstrates building a simple TODO list management application with restish and discusses testing and deploying restish applications.
Designing RESTful APIs
This document provides an introduction to designing RESTful APIs. It discusses HTTP, REST architectural principles, and how to design APIs around resources and use HTTP methods and status codes. Examples of good and bad RESTful APIs are provided, along with exercises to design RESTful versions of existing APIs. Authentication patterns like API keys and OAuth are also covered.
Rest
This document summarizes a workshop on web services and the Richardson Maturity Model (RMM). It explains how a basic web service works by sending an XML request to a server, which decodes it and executes the specified function, then encodes and returns a response. It then describes the four levels of the RMM - from simple request/response using HTTP as a tunnel, to introducing resources at level 1, using HTTP verbs properly at level 2, and finally implementing HATEOAS at level 3 to provide link relations between resources. The document concludes by listing prerequisites for the workshop demo application.
REST library.pptx
The document discusses Representational State Transfer (REST), which is an architectural style for building web services. REST uses commonly used HTTP methods like GET, POST, PUT, PATCH, and DELETE to perform CRUD (create, read, update, delete) operations on resources. These requests use URLs to specify resources and return responses in formats like JSON or XML. The document provides examples of how each HTTP method maps to different CRUD operations and requests and responses using a sample student API.
REST and Web API
The document discusses REST (Representational State Transfer) and the Richardson Maturity Model for building RESTful web APIs. It explains the four levels of the maturity model - from simple request-response (Level 0) to full REST with hypermedia links (Level 3). It then provides an overview of how to build RESTful services with the ASP.NET Web API framework, covering routing, controllers, OData support, and extensibility options.
REST and Web API
The document discusses REST (Representational State Transfer) and the Richardson Maturity Model for building RESTful web APIs. It explains the four levels of the maturity model - from simple request-response (Level 0) to full REST with hypermedia links (Level 3). It also provides an overview of how to build RESTful services with ASP.NET Web API, including URL routing, content negotiation, and extensibility options like message handlers and dependency injection.
HTTPs Strict Transport Security
This document discusses HTTP and HTTPS protocols. It provides information on web servers, HTTP requests and responses, status codes, headers, methods, and SSL/TLS encryption. The key points are:
- HTTP is an application layer protocol for distributed, collaborative hypermedia information systems. It uses a request-response protocol to transfer data between clients and servers.
- HTTP requests consist of a start line with method, URI and version, followed by headers and an optional message body. Common methods are GET, POST, PUT, DELETE.
- HTTP responses contain a start line with status code and reason, followed by headers and an optional message body. Status codes indicate success, redirection, client or server errors.
WebApp #3 : API
The document provides an overview of REST APIs and how they can be used to build web applications. It discusses HTTP and URLs, defines REST and its architectural constraints, and shows how to implement REST principles using HTTP methods, URLs and response codes. The document also covers REST API design best practices like versioning, limiting fields, using JSON format, and handling errors properly. It provides resources for further reading on REST APIs and their implementation.
Why do you need REST
This document discusses REST vs SOAP and recommends ASP.NET Web API for building RESTful services. It explains that REST focuses on resources and HTTP verbs while SOAP defines custom operations. REST uses the existing features of the web like caching and scalability. The document provides examples of SOAP and REST requests and responses. It recommends ASP.NET Web API for building REST services and WCF for SOAP.
HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs
The document provides an overview of the history and evolution of HTTP protocols, from versions 0.9 to 3. It discusses key aspects of HTTP/1.1 including resources, client-server architecture, status codes, and REST. HTTP/2 improvements like multiplexing and binary format are covered. Emerging technologies like GRPC, RSocket, and HTTP/3 which uses QUIC are also summarized. The future of application programming interfaces and network communication is moving towards lower latency protocols built on top of HTTP like HTTP/3 that leverage UDP.
Building Restful Applications Using Php
This document summarizes a presentation about building RESTful applications using PHP. REST (Representational State Transfer) is a software architectural style that uses HTTP verbs to manipulate resources. The presentation covers the six constraints that define REST - client-server separation, statelessness, cacheability, uniform interface, layered system, and code on demand. It provides tips for implementing REST in PHP like using the header() function, determining the request method, and encoding/decoding JSON. Questions from the audience are answered at the end.
REST in ( a mobile ) peace @ WHYMCA 05-21-2011
RESTful architectures and the advantage for HTTP consumers.
Focused on what matters to the mobile world: performances & scalability.
An Introduction To REST API
This document provides an introduction and overview of REST APIs. It defines REST as an architectural style based on web standards like HTTP that defines resources that are accessed via common operations like GET, PUT, POST, and DELETE. It outlines best practices for REST API design, including using nouns in URIs, plural resource names, GET for retrieval only, HTTP status codes, and versioning. It also covers concepts like filtering, sorting, paging, and common queries.
Fulfilling the Hypermedia Constraint via HTTP OPTIONS, The HTTP Vocabulary In...
This document summarizes a presentation on fulfilling the hypermedia constraint in RESTful systems using HTTP OPTIONS requests, representing HTTP requests and responses in RDF, and using link headers. It discusses modeling API specifications and constraints using these techniques to transparently provide documentation and controls to user agents. Examples are given of annotating YouTube video IDs requested from an API with RDF and using link headers to indicate related resources.
Anintroductiontojavawebtechnology 090324184240-phpapp01
This document provides an introduction to Java servlets and web technologies. It discusses HTTP protocols and methods like GET and POST. It explains concepts like web containers, servlet lifecycles, and the structure of web applications. It also provides instructions for setting up a servlet development environment with Java, Tomcat, and configuring the CLASSPATH variable. Finally, it outlines some important servlet API classes and interfaces.
Restful web services
This presentation covers basics of RESTful webservices. I have prepared it by reading different online tutorials. One of them is java brains video tutorial. Hope this helps some one.
If any one needs examples mentioned in the slides, please contact me.
Web Tech Java Servlet Update1
The document provides an introduction to Java web technology and servlets. It discusses HTTP and its request/response model. It describes common HTTP methods like GET and POST, and explains the difference between the two. It also covers the servlet lifecycle, web containers, and setting up a servlet development environment.
HTTP: the Other ESB
Presented at Houston Tech Fest 2009.
Many developers use enterprise service bus (ESB) tools such as BizTalk or, for those looking at a lighter-weight approach, NServiceBus. What many fail to realize is that we have another option, one that has been tried and tested for many years and that we all use daily: HTTP. Find out how HTTP can deliver a much more maintainable, simpler solution to your ESB problems.
An Introduction To Java Web Technology
This document provides an introduction to Java web technology and servlets. It discusses HTTP and its request/response model, HTTP methods like GET and POST, the servlet lifecycle including initialization, request handling, and destruction, and the basic structure of a web application. It also provides an overview of setting up a servlet development environment with Java, Tomcat, and configuring the CLASSPATH.
Similar to How does the Web work? (20)
HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs
HTTP / 1, HTTP / 2 and HTTP / 3: Past, present and the future of APIs
Fulfilling the Hypermedia Constraint via HTTP OPTIONS, The HTTP Vocabulary In...
Fulfilling the Hypermedia Constraint via HTTP OPTIONS, The HTTP Vocabulary In...
Anintroductiontojavawebtechnology 090324184240-phpapp01
Anintroductiontojavawebtechnology 090324184240-phpapp01
More from Guilherme
Where Does the Fat Goes? Utilizando Form Objects Para Simplificar seu Código
The document discusses using form objects to simplify code in monolithic applications. It describes problems with "fat controller" code that handles many responsibilities in a single controller action. This can lead to divergent changes, feature envy, and inappropriate intimacy code smells. The document proposes refactoring code using principles like "slim controller, fat model" - moving logic from controllers to models using form objects. This improves separation of concerns and adherence to rules like short methods and single responsibility classes.
Descobrindo APIs REST
Este documento fornece uma introdução sobre APIs REST, definindo o que é REST e hipermídia, discutindo como projetar e implementar uma API REST passo a passo e mencionando algumas ferramentas e bibliotecas úteis. O documento explica como entender o fluxo de trabalho da API, construir uma máquina de estados, criar tipos de mídia e implementar a API usando exemplos de pedidos e pagamentos em uma lanchonete.
Redu walled garden
Apresentará as motivações e lições aprendidas na criação de uma aplicação de larga escala orientada a serviços. Entenda como fatores como performance, estilos de comunicação e produtividade da equipe relacionam-se à estruturação de uma aplicação.
Desafio de crescer
O documento discute os desafios de crescimento enfrentados pela plataforma de educação a distância Redu, incluindo problemas de velocidade na entrega de novas funcionalidades à medida que a equipe crescia. A arquitetura de microsserviços é proposta como uma solução, separando a aplicação principal em vários serviços autônomos e isolados que se comunicam através de uma fila de mensagens, permitindo times menores e mais ágeis.
Consumindo APIs REST com Ruby
This document discusses consuming REST APIs with Ruby. It provides an overview of REST concepts like resources, representations, uniform interface, and hypermedia. It also covers OAuth 2.0 authentication and making HTTP requests in Ruby. Hands-on examples are given for installing Ruby, managing dependencies with Bundler, and using the OAuth2 and Faraday gems to access REST APIs.
Aplicações tipo Canvas no Redu com Rails
Este documento discute como construir aplicações tipo Canvas com Rails. Ele primeiro apresenta o contexto e o que já foi aprendido sobre Ruby, REST, APIs e introdução ao Rails. Em seguida, discute como implementar autenticação OAuth no Rails usando o gem omniauth-redu, adicionando rotas e controladores para autenticação. Por fim, apresenta referências sobre como construir aplicações tipo Canvas com Rails.
Aplicações sociais usando a plataforma Redu
O documento apresenta a plataforma Redu, que permite criar, compartilhar e discutir conteúdos educacionais de forma colaborativa. A plataforma pode ser usada para desenvolver jogos educativos e recursos abertos, e permite a comunicação entre aplicativos dentro e fora do ambiente virtual.
Introdução aos aplicativos tipo canvas
A plataforma Canvas funciona dentro do Redu como uma rede social de aplicativos, permitindo que desenvolvedores criem aplicativos semelhantes aos do Facebook. Os aplicativos rodam dentro de um iframe e se comunicam com o Redu através de uma API RESTful. A autenticação é feita via OAuth 2.0 e armazenada no LocalStorage do navegador, sendo inicialmente compatível apenas com Firefox e Chrome.
Introdução a plataforma de aplicativos Redu
Slides do workshop sobre construção de aplicativos educacionais utilizando o Redu (http://www.redu.com.br) como plataforma.
FLOSS and Startups
This document discusses how open source software (FLOSS) can help address challenges faced by Redu, a Brazilian startup. It identifies three main problems: lack of skilled professionals fluent in their technologies, lack of synergy between local startups using similar technologies, and boosting their educational applications platform. The document proposes that FLOSS can help by training and connecting professionals through projects, increasing collaboration between startups by having them maintain FLOSS projects, and enabling third-party developers to build on their platform through FLOSS technologies.
Ruby 101 && Coding Dojo
Ruby is a dynamic, object-oriented programming language with a focus on simplicity and productivity. It uses dynamic typing where types are bound to values rather than variables. In Ruby, everything is an object, including numbers and strings. The language is interpreted at runtime, allowing classes and methods to be modified. Common data structures include hashes (like dictionaries) and symbols are used to efficiently represent names. Blocks and procs allow passing chunks of code in Ruby. Testing is commonly done with RSpec and TDD approaches using tools like Bundler and RVM.
Dojo: Sass - Syntactically Awesome Stylesheets
Sass is an extension of CSS that adds features like nested rules, variables, mixins, inheritance and more. It compiles to standard CSS. Sass allows CSS code to be more modular, reusable and maintainable by adding these advanced features. Some key features of Sass include nesting rules to organize selectors hierarchically, defining variables to avoid hard-coded values, creating mixins to reuse CSS declarations, and using Compass to easily include CSS3 properties.
Sass
Sass is an extension of CSS that adds features like nested rules, variables, mixins, inheritance and more. It compiles to standard CSS. Sass allows CSS code to be more modular, reusable and maintainable by adding these advanced features. Some key features of Sass include nesting rules to organize CSS, creating mixins to reuse CSS rules, and using variables to define colors and values that can be changed globally. Sass code is translated to normal CSS for browser compatibility.
CSS first steps
The document discusses CSS concepts like syntax, properties for margins, padding, borders, backgrounds, block-level elements, line-level elements, and float. It explains CSS syntax uses #selectors and {property: value} rules. Margin, padding, and border properties can set spacing and styles. Block elements span the full width while inline elements sit within lines. Float removes elements from the normal flow and positions them left or right, and cleared elements sit below floated ones.
0 introducao padroes_web
Este documento apresenta um curso sobre desenvolvimento web usando padrões da W3C. O curso discute noções gerais sobre padrões web, sua importância e as três camadas de desenvolvimento. Ele será conduzido de forma orientada a projetos com ferramentas como editores de texto e o navegador Firefox com plugins.
Plano de Pesquisa - Redu Respostas
O documento descreve um plano de pesquisa para criar um mecanismo de busca de informações em ambientes virtuais de aprendizagem. O plano inclui objetivos gerais de criar uma ferramenta de social search e estimular contribuições de usuários. Os objetivos específicos incluem entrevistas para entender quando os usuários buscam informações online e o que os motiva a ajudar outros, além de questionários e testes de usabilidade para validar atributos e comportamentos relevantes.
Desevolvimento Web Client-side - AJAX
O documento apresenta uma introdução sobre AJAX com jQuery, explicando que AJAX permite requisições assíncronas em JavaScript para receber dados no servidor, como XML. A complexidade de processamento fica no servidor, enquanto o JavaScript se limita a fazer requisições e atualizar a página. É recomendado usar o servidor XAMPP localmente para exemplificar requisições AJAX.
Desevolvimento Web Client-side - jQuery
Este documento apresenta uma introdução ao jQuery, uma biblioteca JavaScript que simplifica manipulação de elementos HTML, eventos, animações e Ajax. Explica o que é jQuery, como funciona seu ciclo de trabalho semelhante ao CSS, como baixar e incluir o arquivo .js, usar seletores e funções jQuery para modificar conteúdo, estilos e atributos. Também mostra exemplos de efeitos, animações, manipulação de formulários e plugins úteis.
3 padroes-web-intro-javascript
Este documento apresenta uma introdução ao JavaScript, incluindo sua utilização para interagir com o DOM, formas de inclusão e uso de variáveis, operadores, tipos, estruturas de controle como if, while e for, funções, escopo de variáveis e arrays.
More from Guilherme (20)
Where Does the Fat Goes? Utilizando Form Objects Para Simplificar seu Código
Where Does the Fat Goes? Utilizando Form Objects Para Simplificar seu Código
Recently uploaded
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Webinar: Designing a schema for a Data Warehouse
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Project Management Semester Long Project - Acuity
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Recently uploaded (20)
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How does the Web work?
- 1. How does the web work? aka HTTP 101 by Guilherme Cavalcanti @guiocavalcanti
- 2. Schedule 1. Some Web Principles 2. REST 3. HTTP Verbs Idempotency Side effects GET and POST Vs. PUT and DELETE 4. Rails 5. AJAX vs. Accessibility
- 3. Some Web Principles Universality Any resource anywhere can be given a URI Any resource of significance should be given a URI. Resources are documents As well as concepts and abstract ideias (Semantic Web) Global Scope It doesn't matter to whom or where you specify that URI, it will have the same meaning.
- 4. REST Architectural style coined by Roy Fielding (phd dissertation)5 State transference At any particular time, a client can either be in transition between application states or "at rest". A client in a rest state is able to interact with its user, but creates no load and consumes no per-client storage on the servers or on the network4 The HTTP portocols uses the rest style
- 5. HTTP Verbs Side effect change or not the state of the world Idempotency the side-effects of N > 0 identical requests is the same as for a single request
- 6. HTTP Verbs Idempotent Cacheable Side effects GET x x POST x PUT x x DELETE x
- 7. HTTP: RESTful services vs lack of verbs PUT Put ssomething at some place Updates something PUT http://redu.com.br/spaces/my-space Content: My new Space POST The server decides which action gonna be taken POST http://redu.com.br/spaces/filter Content: name=my;audience=[higher-edu,sat] DELETE Deletes some resource DELETE http://redu.com.br/spaces/my-space
- 8. HTTP: RESTful services vs lack of verbs Doesn't work on6 < HTML 4 < XHTML 1.0 It works on XMLHttpRequests (aka AJAX)3
- 9. HTTP: RESTful services vs lack of verbs POST acting as PUT POST http://redu.com.br/spaces Content: name=My Space;path=my-space POST acting as PUT when updating POST http://redu.com.br/spaces/my-space Content: _method=PUT POST acting as DELETE POST http://redu.com.br/spaces/my-space Content: _method=DELETE
- 10. How Rails deals with it? Edit:
- 11. References 1. Why put and delete? 2. HTTP RFC 3. Verbs support 4. REST 5. Roy's dissertation 6. Useful question at Stackoverflow