The document discusses several Grails plugins: Console, DB Migration, Remote Pagination, and Asset Pipeline. The Console plugin provides an interactive Groovy console for debugging. The DB Migration plugin helps manage database changes using Liquibase. The Remote Pagination plugin adds tags for remote pagination. The Asset Pipeline plugin handles processing and minification of CSS and JavaScript assets.
Introduction into service oriented web development using OSGi, includes latest Declarative Services (DS) and the Http Whiteboard Specification.
OSGi Community Event 2014 Abstract: The new HTTP Whiteboard API is a significant improvement over Http Service 1.2. In this talk we'll explore the uses and benefits of the new API and how that this should have been what java webapps were from the start.
This document discusses the new features of ASP.NET 5, the next major version of ASP.NET. It introduces the new modular architecture and project structure. Key features covered include support for non-Windows platforms, a leaner core CLR runtime, configuration and dependency injection improvements, front-end workflow changes using Bower and Grunt/Gulp, and new MVC and tag helper features. The goal of ASP.NET 5 is to make ASP.NET more modern, modular and cross-platform.
The document discusses using Protocol Buffers over HTTP for making synchronous API calls from an App Engine application to a backend service. It describes how ApiProxy and Delegate classes are used to make the calls, with the request and response encoded as Protocol Buffers and sent as HTTP requests. The backend service receives the request, decodes the Protocol Buffer, makes the API call, encodes the response as a Protocol Buffer, and returns it to the application via an HTTP response. This allows App Engine applications to make synchronous calls to backend services using Protocol Buffers over HTTP.
The document discusses the Open Service Broker API and Kubernetes Service Catalog. It describes how the Service Broker API allows developers to provision and bind to services outside of Kubernetes. It then explains how the Kubernetes Service Catalog implements the Service Broker API to provide services within Kubernetes using new resource types like ServiceInstance and ServiceBinding. The document provides examples of installing brokers, listing available services, and creating instances and bindings.
Outline - What Is Selenium - Why Automates Web Browser - Automation with Selenium IDE - Automation with WebDriver - Page Factory - Page Object Pattern - Automation with FluentAutomation - Selenium Grid - Selenium Tests in Continuous Integration - The Reality - Q & A Code sample can be downloaded at http://goo.gl/KtyF6r
The document contains an XML configuration file that defines connection string and role provider settings. The connection string specifies a SQL Server database named "aspnetdb" on server "GELIS-WIN2008R2" using integrated security. A SQL role provider is configured to use this connection string under the name "LocalSqlServer". Links to additional Asp.Net identity and membership provider resources are also included.
Service Workers is coming. Bring your own magic with the first programmable cache in your script, and more! Presented at the GDG Korea DevFest 2014 on the 31st of May 2014: https://sites.google.com/site/gdgdevfestkorea2014/
There are number of customers who have requirements to start using the audit function, and many of them are concerned it would affect the entire Alfresco repository performance, which maybe true. Actually we don’t have to enable it since most of the user activities are already tracked by the other out of the function named activity_feed. That is already running. I would like to talk about what the differences are, what event items we can get for each of them from the APIs, and Database point of view. And how we should maintain the records to prevent them from having the performance issue.
My presentation done on Windows Phone App Camp Lithuania. I was also helping as a mentor. It was very interesting experience for me.
The document discusses how HipChat improved their web client development process. It describes moving from a monolithic codebase with no testing to using React for component-based development with JSX syntax. This improved reusability, performance, and made the code easier to read. It also implemented Flux architecture and separated concerns into stores, actions, and dispatcher. Additional improvements included using Webpack for builds, Gulp for testing and documentation, and feature branches to streamline development and deployment. These changes allowed HipChat to deploy the web client more frequently and identify issues faster.
This presentation provides overview of new asp.net web api, comparing with MVC, and go through features of web api such as Content Negotiation, Queryable, Html help page, and more.