Module: Buffet

Defined in:
lib/buffet.rb

Overview

TERMINOLOGY

Proxy Interface

  • the class that defines the methods implemented by each proxy

Proxy Implementation

  • a "concrete implementation" of the "abstract" Proxy "interface" for an individual 3rd-party service

Proxy

  • shorthand for Proxy Implementation

TO DO

  • Write a companion gem called "meal ticket" to handle 3rd-party auth

NOTES / OPEN QUESTIONS

Maintain record of copies across services?

When writing an object out to a service, can/should we track that it's the same as the one we pulled from another service? Eg, if I pull a photo from FB and post it to Flickr, from the user's perspective I've duped the photo in the second location but programatically, they're two different things. So for instance if we were to then show all photos for a user, we'd show it twice. Is that correct? Should we only show it once? Not sure how we'd be able to persist those connections. Maybe there's a way we could link them in their metadata? When we push the photo to flickr, give it some hidden value that lets us associate it with the FB version?

Non-standard response snippets

We've floated the idea of having pure types include a hash of "extras". This would be data returned by a given service that doesn't fall within the generic feature set we've defined but nonetheless might be useful to a developer. We want to make this information available, but not TOO easy to get to, because after all, the whole point of this gem is to standardize. But hopefully the extras hash will make life easier for developers who want a little more control, and also help us determine what features we should add to the official feature set.

Defined Under Namespace

Modules: User Classes: Album, FlickrProxy, Image, ProxyInterface