Skip to content

Instantly share code, notes, and snippets.

@hdp
Created April 23, 2009 02:35
Show Gist options
  • Save hdp/100246 to your computer and use it in GitHub Desktop.
Save hdp/100246 to your computer and use it in GitHub Desktop.
hdp's free software todo list
* allow people to configure individual de/serializers
* fix handling of incoming vs. outgoing Content-Type
right now the incoming Content-Type header takes top priority for both
deserialization and serialization. This is wrong per the RFC; the way the
client should specify what it wants is via the Accept header. deprecation
cycle.
* keep refactoring things into roles
* serialize/deserialize deserve their own dist
maybe two dists: one for the basic de/serialization and one for Catalyst glue.
why not Data::Serializer?
a) supports a bunch of formats I don't care about
b) asks lots of questions
c) has options we don't care about
* HTTP response encapsulation with per-status validation (joel was going to
start this?)
* move things out of controller/action and into request/response
* should REST be a view?
why should "serialize to YAML" bypass the View step, when a normal TT or Mason
view is essentially "serialize to HTML"?
(I should come up with compelling use cases before spending too much time
tilting at this windmill.)
* write plugins for my personal release cycle, git integration, etc.
* move more dists to dzil
* write single-step bootstrapper into a given target directory (download and
everything)
* figure out why some installs with too-old CPAN.pm fail mysteriously and
result in complains about being unable to write to "/sources"
(e.g. perl 5.8.8)
* FeyX::Active, but somehow awesomer
* Fey::Dumper -- write a Fey::Schema to a Perl class
* generic REST client (LWP::REST?), plus Catalyst::REST glue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment