Group items tagged

"Blueprints is a property graph model interface. It provides implementations, test suites, and supporting extensions. Graph databases and frameworks that implement the Blueprints interfaces automatically support Blueprints-enabled applications. Likewise, Blueprints-enabled applications can plug-and-play different Blueprints-enabled graph backends."

"Scalastic is an interface for ElasticSearch, designed to provide more flexible and Scala-esque interface around the native ElasticSearch Java API."

Lsyncd watches a local directory trees event monitor interface (inotify or fsevents). It aggregates and combines events for a few seconds and then spawns one (or more) process(es) to synchronize the changes.

Simple and flexible HTML, CSS, and Javascript for popular user interface components and interactions.

Backbone.js gives structure to web applications by providing models with key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface.

Herramienta de diseño visual de interfaces de usuario web. Incluye soporte para utilizar componentes de varios frameworks javascript populares como dojo, jqueryui, yui, etc. Muy recomendado!

ble Vector collections provides a referentially transparent interface to arrays); and use buffers instead of direct sequence cons

Reactive-web is a new framework for writing highly interactive and dynamic web applications. It's written in Scala , sits on top of Lift, and uses the Functional Reactive Programming library reactive-core (it's in the same repository). As in GWT, you can code the user interface in the same language as the rest of your application (except in Scala instead of Java), rather than writing JavaScript. Unlike GWT, however, you don't need an extra build step to convert your code to JavaScript. You can easily combine code that runs on the browser with code that runs on the server. And, you can declare dynamic relationships between components, like binding in Flex/JavaFX/etc. (only much more powerful).

"Graph for Scala is intended to provide basic graph functionality that seamlessly fits into the Scala standard collections library. Like the other members of scala.collection, Graph for Scala is an in-memory container that exposes a user-friendly interface without sacrificing functionality or flexibility. Graph for Scala also has ready-to-go implementations of JSON-Import/Export and Dot-Export - more popular graph serialization formats are coming soon. In addition, other powerful tools such as graph databases emulation and distributed graph processing are due to be supported."

"Protostuff is the stuff that leverages google's protobuf. A serialization library with built-in support for forward-backward compatibility (schema evolution) and validation. available formats: protostuff (native) graph (protostuff with support for cyclic references. See SerializingObjectGraphs) protobuf json smile (binary json useable from the protostuff-json module) xml yaml (ser only) kvp (binary uwsgi header) support for messages that are generated by the protostuff-compiler (java_bean) cyclic references via graph format see CompilerOptions for more customized compilation of .proto files support for existing pojos (See runtime schemas) cyclic references via graph format polymorphic (a nested message can be an interface/abstract class or even java.lang.Object) support for existing protoc-generated java messages see the io instructions for json, xml, yaml) no support for cyclic references (limitation of the builder pattern) Interoperability across various mobile platforms android kindle j2me (protostuff-me module) Transcoding support converts one encoding to another. See PipeUsage. Source and Sink protostuff, protobuf, json, json-numeric, smile, smile-numeric, xml Sink only yaml "

"The integration between git and Subversion (git-svn) is so well done that several of us have been using git as our interface to all our Subversion repositories. Doing this is fairly simple, but there are some interesting tricks, and so I thought I would share a day in the Viget life with git-svn."

"Discover an entirely browser-based interface for your data."

"In Forrester's 40-criteria evaluation of application programming interface (API) management solutions, we identified the 11 most significant software providers in the category - 3scale, Apigee, Axway, CA Technologies, IBM, Informatica, Intel Services, MuleSoft, SOA Software, Tibco Software, and WSO2 - and researched, analyzed, and evaluated them. This report details our findings about how well each vendor's products fulfill our criteria and where they stand in relation to each other. This analysis, combined with three buying guides that highlight key make-or-break decision factors, will help AD&D professionals select the right partner for their API management needs."

"Colossus is a lightweight framework for building high-performance applications in Scala that require non-blocking network I/O. In particular Colossus is focused on low-latency stateless microservices where often the service is little more than an abstraction over a database and/or cache. For this use case, Colossus aims to maximize performance while keeping the interface clean and concise."

Google publicó el primer preview de su nuevo lenguaje. Soporta 2 ambientes de ejecución: una nueva virtual machine y compilado a javascript. La VM soporta startups muy rápidos leyendo el estado del sistema desde archivos de imagen estilo smalltalk. El lenguaje es OO pero basado en interfaces, no clases (aunque tiene clases, todos los method dispatch se refieren a una interfaz). El tipado estático es 100% opcional, permite no poner tipos e incluso permite ejecutar código que no valide el typechecker (con errores). El modelo de ejecución es tipo erlang como procesos single-threaded aislados unos de otros (no pueden compartir nada) que solo se comunican pasando mensajes, éstos se llaman "Isolates".

What is Graphite? Graphite is a highly scalable real-time graphing system. As a user, you write an application that collects numeric time-series data that you are interested in graphing, and send it to Graphite's processing backend, carbon, which stores the data in Graphite's specialized database. The data can then be visualized through graphite's web interfaces. Who should use Graphite? Graphite is actually a bit of a niche application. Specifically, it is designed to handle numeric time-series data. For example, Graphite would be good at graphing stock prices because they are numbers that change over time. However Graphite is a complex system, and if you only have a few hundred distinct things you want to graph (stocks prices in the S&P 500) then Graphite is probably overkill. But if you need to graph a lot of different things (like dozens of performance metrics from thousands of servers) and you don't necessarily know the names of those things in advance (who wants to maintain such huge configuration?) then Graphite is for you.

Ostrich is a library for servers that makes it easy to:  * load & reload per-environment configuration  * collect runtime statistics (counters, gauges, metrics, and labels)  * report those statistics through a simple web interface (optionally with graphs) or into log files  * interact with the server over HTTP to check build versions or shut it down

"Internet Routing: It's a program (well, a daemon, as you are going to discover in a moment) which works as a dynamic router in an Internet type network (that is, in a network running either the IPv4 or the IPv6 protocol). Routers are devices which forward packets between interconnected networks in order to allow hosts not connected directly to the same local area network to communicate with each other. They also communicate with the other routers in the Internet to discover the topology of the network which allows them to find optimal (in terms of some metric) rules for forwarding of packets (which are called routing tables) and to adapt themselves to the changing conditions such as outages of network links, building of new connections and so on. Most of these routers are costly dedicated devices running obscure firmware which is hard to configure and not open to any changes (on the other hand, their special hardware design allows them to keep up with lots of high-speed network interfaces, better than general-purpose computer does). Fortunately, most operating systems of the UNIX family allow an ordinary computer to act as a router and forward packets belonging to the other hosts, but only according to a statically configured table."

"URI.js is a javascript library for working with URLs. It offers a "jQuery-style" API (Fluent Interface, Method Chaining) to read and write all regular components and a number of convenience methods like .directory() and .authority(). URI.js offers simple, yet powerful ways of working with query string, has a number of URI-normalization functions and converts relative/absolute paths. While URI.js provides a jQuery plugin. URI.js itself does not rely on jQuery. You don't need jQuery to use URI.js"

Hola!. La vi el viernes a la manyana la libreria esta.Parece que esta buenisima. respecto a lo que yo tenia que hacer obviamente que puede ayudar con las funciones relative y absolute, pero por lo que definimos, "Construir las url's de los recursos a partir del raiz de la libreria", descarte su adopcion por parecerme de alguna forma "sobrecarga".Sea como sea, es una buena herramienta para adoptar. Buen finde.

Me acabo de dar cuenta.... Este articulo lo pusiste el 4. Estamos a la noche del 5 y recien me notifico. No es la primera vez, y ahora sospecho que son todas las veces las que cosas compartidas en diigo que se notifican con demora. Porque sera?

"Super-easy Wireframing. Design, collaborate user interface concepts for your apps and websites."