Jacob
Jay
Jacob Jay

Peripatetic British designer, full-stack developer and entrepreneur.
      Specialising in web application architecture and user-experience.

7 Server projects

B2B Rental Marketplace for UK Enterprise

Bring an existing business and its processes online and up-to-date using a marketplace mediating with third-party suppliers.

Innovations

  • Multiple pricing and comission models to support both owned assets and third-party assets
  • Per-class (category, product or variant) cascading inherited attributes, with ancestor and descendant overrides providing a variety of ways to control how suppliers add new items and values
  • Mediated messaging, with client-supplier messaging relayed through an operator
  • Supplier auctioning with deferred (countdown) booking assignments in cases of unknown availability
  • Collection options using geolocation
  • Flexible delivery class calculations assignable per-category and postcode
  • Geographical search ranking availability of items with delivery constraints
  • Ability for an operator to easily swap their CMS view to that of a supplier (delegate authentication) when handling operations by telephone

Features

  • Categorised product (and variant) listings with search
  • Bespoke CMS handling categories, products and their variants with dynamic attributes
  • Booking functionality (not calendared)
  • CMS and API for suppliers
  • Mobile app with push notifications and messaging for suppliers and customers
  • Multi-device and multi-role authentication and notification settings
2014 — Architecture, Web, E-commerceSummary ↙︎
Details, 10 images

Moonstalk for The Moon Mill

Open-source web development framework and hosting stack using Lua.

Features

  • Automated filesystem to URL mapping for sites and applications, with no configuration necessary before use (including web server)
  • Includes a bespoke low-latency NoSQL database which shares the web application environment and functions, whilst also supporting a task queue with seperate processes
  • Internationalisation and localisation including handling for plurals and GeoIP
  • Best-practice handling of script-loading, CDN assets, canonical tags, addressing, salted passwords, microcaching, deployment (via dCVS), etc.
  • Many supplementary applications providing functionality ranging from calendaring to geospatial search

Links

2010 — Conception, Server, APISummary ↙︎
Details, 2 images

ProfileConnect Gateway API for Verse

Abstract API methods from across multiple third-party prodivders into a normalised set of methods for use by clients with either intermediary gateways or end service providers.
Function
API

Innovations

  • Unlike the MediaSock specification which concerns itself with only endpoints (client and server), this specification attempts to deal predominantly with intermediaries (gateways), yet also still offers endpoint functionality. Thus its methods might be used alongside existing API methods fufilling specific functions (whether provider-specific, or generic such as MediaSock), or in a completely-abstract manner on their own to fufil the same functions. However in such an abstract manner the method naming does not reveal the functionality offered by a provider, as compared to non-abstract APIs, instead it must be discovered using introspection, or hard-coded relying upon established behaviours or assumptions.

Links

2008 — Conception, Server, APISummary ↙︎
Details, 0 images

API Gateway for Pixelpipe

An API gateway server accepting media uploads from clients using a wide variety of supported APIs, and re-broadcast them to well over 50 different service providers.

Innovations

  • Deferred batching to accept multiple uploads over a configurable timeframe, and then re-broadcast them together as an album or single blog post after no more items had arrived (instead of individually upon arrival).
  • Utilisation of special 'routing' tags, allowing uploaded media to be dispatched to specific accounts or groups of accounts simply using a tag, thus avoiding the need for specific client routing UI, and instead using a client's native tagging UI.

Features

  • Prioritised image processing queue with service provider connection constraints
  • Service provider error aggregation and reporting to quicly idenitfy and prioritise API issue resolution with destination service providers
  • Support for multitudinous client upload APIs including metaweblog and Flickr, which with DNS spoofing enabled official clients to be used with the server
  • Bespoke upload applications and Plug-ins including iPhone, Aperture, Windows Live Gallery and integration with Nokia share
  • Support for hosting uploads directly on the service, including views for user streams, albums and individual photos
2008 — Management, Server, PhotoSummary ↙︎
Details, 7 images

MediaSock Client Framework for Verse

Abstraction framework for media-sharing web-services, utilising loadable modules, and a flexible properties architecture.
Function
Photo Framework API

Innovations

  • First library to enable use of common code and functionality with disparate service providers.
  • Simultaneous classed data and string handling (suitable for AJAX-type web server deployment scenarios as well as desktop).
  • Was deployed on a Flex server platform, and in a .NET desktop application.

Features

  • Standardised functionality: list/make albums, list/download/upload media.
  • Initially available with modules for Webshots, Flickr, and Yahoo! Photos.
  • Session saving (service dependant).

Links

2006 — Conception, Server, PhotoSummary ↙︎
Details, 0 images

MediaSleeve API for Verse

Define a specification by which online content providers such as radio streams, may provide metadata (e.g. album covers, song details) to client applications.
Function
API

Links

2005 — Conception, Server, APISummary ↙︎
Details, 0 images

MediaSock Protocol for Verse

Lightweight service discovery protocol and web-service API to facilitate handling a user's media assets.
Function
API

Innovations

  • clients can utilise service discovery not only check with a low cost (i.e. via HTTP HEAD) if a provider supports the protcol, but also what methods and characteristics are supported by that provider (interoperability between clients and servers is notably not guarenteed by the protocol)
  • designed from the outset for easy implementation by service providers; could be implemented simply atop existing page forms, using existing cookies for authentication and utilising other common API methods instead of requiring new implementations

Features

  • choice of implementation models for service providers
  • fixed-string XML and values allow parsing of responses without requiring a heavyweight XML parser

Links

2005 — Conception, Server, APISummary ↙︎
Details, 0 images