ENGAGE-247: Improve Engage's data access layer, removing redundancy across services

Metadata

Source
ENGAGE-247
Type
Improvement
Priority
Major
Status
Closed
Resolution
Won't Fix
Assignee
Colin Clark
Reporter
Michelle D'Souza
Created
2010-01-18T15:22:49.000-0500
Updated
2017-12-22T09:44:32.413-0500
Versions
  1. 0.1
  2. 0.3b
Fixed Versions
  1. 0.3
Component
N/A

Description

This is an umbrella issue for a two-day timeboxed task to improve the overall design of Engage's Kettle-side services and remove the redundancy within them. Will also include refactoring the data mapping layer to be more generic and extensible.

Attachments

Comments

  • y z commented 2010-01-25T17:43:09.000-0500

    This is a sketch attempt to remove redundancy across the services in kettle, demonstrated on services for browse

  • Antranig Basman commented 2010-01-29T14:53:55.000-0500

    Thanks for this patch - I can see two main issues, firstly that the return of genuine data cannot be reliably distinguished from an error return, and secondly that the pattern of factoring of service construction is upside-down - the services should be created from configuration, rather than proving utilities to call from within existing services. I have made an initial implementation of "fluid.kettle.getData" now within kettle.js as required by the I18N bundle work...

  • Justin Obara commented 2010-03-17T11:47:36.000-0400

    Bug Parade Engage 0.3

  • Justin Obara commented 2017-12-22T09:44:32.412-0500

    The repository has been archived.