25+ Reasons to use OmniFaces in JSF applicationsAnghel Leonard
OmniFaces is an utility library that can help you to improve your JSF development experience. This presentation reveals 25+ real cases in which OmniFaces can make JSF life easier.
.net training | learn .net | Microsoft dot net Course | Microsoft dot net onl...Nancy Thomas
Website : http://www.todaycourses.com
.Net Online Training Concepts :
NET FUNDAMENTALS
Why .NET?
The .NET initiative
Introduction to .NET framework
Advantages of .NET framework
System requirements
.NET FUNDAMENTALS
Why .NET?
The .NET initiative
Introduction to .NET framework
Advantages of .NET framework
System requirements
INTRODUCTION TO VISUAL STUDIO .NET
Base class libraries
Common language-runtime (CLR)
Microsoft intermediate language (MSIL)
Optimized just-in-time (JIT)
Common type systems (CTS)
Common language specification (CLS)
Compilation and execution of .NET application
Assemblies
Namespace
25+ Reasons to use OmniFaces in JSF applicationsAnghel Leonard
OmniFaces is an utility library that can help you to improve your JSF development experience. This presentation reveals 25+ real cases in which OmniFaces can make JSF life easier.
.net training | learn .net | Microsoft dot net Course | Microsoft dot net onl...Nancy Thomas
Website : http://www.todaycourses.com
.Net Online Training Concepts :
NET FUNDAMENTALS
Why .NET?
The .NET initiative
Introduction to .NET framework
Advantages of .NET framework
System requirements
.NET FUNDAMENTALS
Why .NET?
The .NET initiative
Introduction to .NET framework
Advantages of .NET framework
System requirements
INTRODUCTION TO VISUAL STUDIO .NET
Base class libraries
Common language-runtime (CLR)
Microsoft intermediate language (MSIL)
Optimized just-in-time (JIT)
Common type systems (CTS)
Common language specification (CLS)
Compilation and execution of .NET application
Assemblies
Namespace
Online shopping (sometimes known as e-tail from "electronic retail" or e-shopping) is a form of electronic commerce which allows consumers to directly buy goods or services from a seller over the Internet using a web browser. Alternative names are: e-web-store, e-shop, e-store, Internet shop, web-shop, web-store, online store, online storefront and virtual store. Mobile commerce (or m-commerce) describes purchasing from an online retailer's mobile optimized online site or app.
Online shopping (sometimes known as e-tail from "electronic retail" or e-shopping) is a form of electronic commerce which allows consumers to directly buy goods or services from a seller over the Internet using a web browser. Alternative names are: e-web-store, e-shop, e-store, Internet shop, web-shop, web-store, online store, online storefront and virtual store. Mobile commerce (or m-commerce) describes purchasing from an online retailer's mobile optimized online site or app.
Slides from my talk at the Feb 2011 Seattle Tech Startups meeting. More info here (along with powerpoint slides): http://www.startupmonkeys.com/2011/02/scala-frugal-mechanic/
Real time Analytics with Apache Kafka and Apache SparkRahul Jain
A presentation cum workshop on Real time Analytics with Apache Kafka and Apache Spark. Apache Kafka is a distributed publish-subscribe messaging while other side Spark Streaming brings Spark's language-integrated API to stream processing, allows to write streaming applications very quickly and easily. It supports both Java and Scala. In this workshop we are going to explore Apache Kafka, Zookeeper and Spark with a Web click streaming example using Spark Streaming. A clickstream is the recording of the parts of the screen a computer user clicks on while web browsing.
Lessons from the Trenches: Engineering Great AJAX Experiencesgoodfriday
Explore the challenges and lessons learned developing the Windows Live and Gadgets Web client frameworks powering Windows Live, Hotmail (Kahuna beta), Spaces, and more. This technical talk presents design and architectural considerations for building interactive AJAX-like sites. See how componentization, network management, accessibility, page composition, and more impact the design and engineering of your Web application.
Tuning and optimizing webcenter spaces application white paperVinay Kumar
This white paper focuses on Oracle WebCenter Spaces performance problem and analysis after post production deployment. We will tune JVM ( JRocket). Webcenter Portal, Webcenter content and ADF task flow.
Everyone knows Monad but there is something also very useful and sometimes more powerful – Applicative Functors. I’m going to go from theory to real use cases where Applicative solved my issues.
In this presentation, Łukasz explains what exactly API Gateway is and debates about many problems that it actually can solve. He uses AWS API Gateway as an example.
Do ECTL not ETL: the art and science of data cleansing in data pipelines by P...Scalac
Many companies struggle to get some business knowledge from their data. They know they have data, but then what? They even know what to extract from the data, but guess what happens? Garbage in - garbage out. ETL is a known approach for transforming data, but it has a number of drawbacks. One should also know the further reviews of it like ECTL and ELT. We will go through them and also discuss the usual problems with starting data processing in different industries. In this talk, Piotr wants to show the typical mistakes companies make when trying to build their data warehouse, and why small companies fail to even start building their business on their data.
Introduction to Scala by Piotr Wiśniowski ScalacScalac
Po tej prezentacji będziesz mógł/a odróżnić kod funkcjonalny od niefunkcjonalnego i zrefaktorować własne metody, by spełnić wymagania funkcjonalnego kodu i czerpać z niego korzyści!
Actors are one of the most popular concurrency models in nowadays software systems. In this talk, we will present zio-actors – a small strongly typed actor library backed by ZIO. He will explain library design, demonstrate its usage, and point out the differences and similarities with Akka.
Why functional programming and category theory strongly matters - Piotr Parad...Scalac
Niektórzy twierdzą, że SOLID w extremalnej postaci to właśnie FP, Greg Young twierdzi, że CQRS i ES to jest FP.
Programiści FP utrzymują, że Design Patterns są potrzebne, bo w OOP brakuje pewnych konstrukcji.
Sami używają abstrakcji matematycznych z teorii kategorii w sposób zbliżony do wzorców.
Opowiem czym jest FP i jakie supermoce daje.
Pokażę abstrakcje matematyczne z teorii kategorii: Category, Functor, Natural transformation, Monad.
Jak zostały one wykorzystane w oryginalnych publikacjach (functional pearls) używając języka Scala.
(Znajomość Scala nie jest potrzebna.)
Pokaże, też inne często używane w FP abstrakcje z algebry abstrakcyjnej (Monoid, Semigroup, Foldable, Traversable).
Dam też, przegląd mniej znanych ale bardzo ciekawych abstrakcji z teorii kategorii: Comonad, Contravariant, Bifunctor, Profunctor
oraz konstrukcji: Product, Coproduct, Free, Coyoneda.
Myślę, że zarówno doświadczeni programiści jak i osoby nowe dostaną solidną porcję nowych narzędzi do pisania i projektowania oprogramowania.
Może, uda się zobaczyć wzorce projektowe i dobre zasady OOP w nowym świetle :)
Big picture of category theory in scala with deep dive into contravariant and...Scalac
A big picture of category theory in Scala - starting from regular functors with additional structure (Apply, Applicative, Monad) to Comonads. Usually, we think about structures like Monoids in a monoidal category with particular tensor. In here I analyze just signatures of different abstractions.
Exploration of Contravariant functors as a way to model computation "backward" or abstract over input with the ability to prepend operation. Examples for predicates, sorting, show and function input (or any other function parameter except the last one).
Profunctors as abstraction unifying Functors and Contravariant functors to model both input and output. Example for Profunctor - function with one argument.
Relation to Bifunctors, Kan extensions, Adjunctions, and Free constructions.
How to write automated tests and don’t lose your mind by Dorian Sarnowski ScalacScalac
Jak pisać testy i nie zwariować?
Pragmatyczne podejście do pisania testów z punktu widzenia programisty. Garść przemyśleń i dobrych wzorców wyniesiona z dotychczasowych projektów oraz opis najczęściej popełnianych błędów i pułapki, które na nas czyhają.
Do you have that Spark in your ECTL? by Piotr Sych ScalacScalac
Sometimes there is a need for a simple, high-level implementation of ECTL in Spark with a lightning-fast introduction to Spark concepts. study based on a real story. I wish to present an idea of dealing with multiple input formats and structures in a unified approach using Spark. As a result to use it in your Data Science oriented environment as a preparation step for further analyses and experiments. Such a way of handling non-production data inputs particularly helped with providing data quality analyses and conducting experiments on production-like sized datasets without the need of "testing on production" mess.
Typed Actors is a topic that thrills the Scala community for a long time. There were several attempts (that I know of) to implement them but the last one seems to be the one that succeeds. Moreover - despite of status "May change" recently a course on Coursera was published. In my presentation, I'm going to show how the API looks and solutions to common problems.
8. Web Framework Manifesto A quick and easy way to map between a relational database and the target application. Rails' ActiveRecord is a really great example of how to map a relational database. Sure, you might want to use Magma with Squeak for true object persistence, but for most applications in most of the world, you've got a relational database on the back end and you've gotta map to it. The mapping should “do the right thing by default” and all the schema and class information should live in 1 or at most 2 (e.g., migrations and model class) places. Easy, “right by default,” HTTP request mapping. A request comes in and gets routed to the right place. This is another place that Rails really shines (at least at the “page” level.) PHP and JSP also do well here. Schemes (like Struts) that require 35 configuration files, etc. to say “/foo/bar/33” gets routed to the Bar method on the Foo controller are way to complex. Seaside takes this to yet a better level... requests get mapped to the right closure in the right component. But I digress. Automatic “view” selection and composition. Basically, the “right by default” view should be selected based on the request, but alternate views should be specified by the “controller.” Views should be CSS friendly. I'm split over having separate template files (e.g., Rails, JSP, etc.) or embedding the HTML in the file (e.g., Seaside) or having both options (Erlyweb.) Pages must be composed of arbitrary components that manage their own state. This means that the search panel, the scrolling “what's hot” area, the catalog, and the shopping cart are all separate components. Seaside really excels in this area. Check out the Seaside Sushi store demo that demonstrates many different components with different state all on the same page. Remember also, that the component nature of the page means that the components each receive their own UI messages. This is a place where Rails does not excel. The rendering of components must be asynchronous based on user-based and external event-based state change. This means that if state changes in the component, the UI should be updated. Maybe it's updated the next time the page is reloaded (this is the way Seaside's Sushi store works,) the next time there's an AJAX request made, or via a Comet push. The components should be agnostic to the update mechanism. They should merely mark themselves as dirty and be re-rendered the next time there's an opportunity. Components should be live (or seamlessly persisted) at all times, ready to respond to events. The browser should be honored and feared. That means the back button should “do the right thing” (see Seaside) and input from the browser should never be trusted, but should always be tested, validated, and destroyed if it is unexpected (e.g., throw away a POST that contains parameters that were not in the form presented to the user.) There should be a single way of describing input validation. That validation should happen whenever possible on the client, but should always be repeated on the server and before any model state is modified. Mapping between object fields and HTML (or whatever the presentation layer is) should be “right by default” and should be extensible based on new technology. Rails and view helpers rule here. There should exist an orthogonal security layer such that objects that are not accessible to a user should never be returned in a query for the user and fields on an object that are not accessible should not be visible. The security and access control rules should be algebraic and demonstrable during a security audit. This means that neither the view nor the controller should have to test for access control. Objects and requests should be sanitized before they get to the “controller.” Code should be impervious to a replay attack. That means that fields in forms should have random names that change for each request. There should exist a simple, unified way to describe modal user behavior (e.g., filling out a multi-page form.) Seaside rules in this respect. Sessions should be tied to a browser window/tab, not to a browser session. Once again, Seaside really rules on this count. The framework and runtime should correctly and gracefully deal with non-ASCII characters. Deploying the web application should be as simple as putting a file in a known location (e.g., a WAR file on a J2EE server) or by executing a single command (e.g., Capistrano.) Deployments should contain all dependencies such that as long as the target system meets a particular minimum specification (e.g., running Java 1.4 and Tomcat 5.5), the application will work without having to load other configuration files. Deployment and management should be able to be done via command line or a web browser and should never require VNC or some other screen-cast or screen scraping. Testing should be an integral part of the framework and should allow simulating HTTP requests. Rails has the best testing framework of any web development framework I've seen. The production environment should support modern technology including executing multiple threads in a single process and allowing for many “live” objects to be corresident (an absolute necessity for Comet-style applications.) The production environment should support hot code replacement such that new code can be placed in production without impairing existing user state. The development environment should support hot code replacement such that once a file is saved, it becomes live at the next HTTP request. Sure, it may be compiled and moved to the app server on save (Eclipse does this with Java code) but the developer should not have to explicitly compile, restart, reload in order to test a change. The system should be able to map input from a variety of different formats (SOAP, REST, SMTP, etc.) such that requests are normalized and responses are sent over the appropriate medium. There should exist a mechanism for adding functionality to the system with few or no API calls. Rails Engines are an example of this. Subsystems and added functionality should be defined by a clear interface that can be tested and validated during a compile or test cycle. Using parts of the subsystems that are not defined by the interface should be flagged during the test or compile cycle.