These are chat archives for damianh/Cedar

28th
May 2015
Damian Hickey
@damianh
May 28 2015 14:34
Yeah.
Can do it there, but think I'd like a more explicit extension point for Type -> Content-Type (particularly wrt to various versioning patterns)
João Bragança
@thefringeninja
May 28 2015 14:41
i'm already using a different pattern for that thing i'm working on :smile:
Damian Hickey
@damianh
May 28 2015 14:42
Different versioning pattern? :scream:
João Bragança
@thefringeninja
May 28 2015 14:43
yes. application/vnd.ClrNamespace.SomeBoundary.v1.MessageName+json
Damian Hickey
@damianh
May 28 2015 14:43
No
João Bragança
@thefringeninja
May 28 2015 14:43
yes
Damian Hickey
@damianh
May 28 2015 14:43
That is non-standard
João Bragança
@thefringeninja
May 28 2015 14:43
only because that's how the code is arranged and i am too lazy to get it to generate the other way
Damian Hickey
@damianh
May 28 2015 14:44
Fix your lazyness :)
João Bragança
@thefringeninja
May 28 2015 14:44
does it matter? it's just a string and this string should be provided by the server
Damian Hickey
@damianh
May 28 2015 14:44
Should be provided by client too
João Bragança
@thefringeninja
May 28 2015 14:44
is cedar a framework or a library? :trollface:
Damian Hickey
@damianh
May 28 2015 14:44
a libwork
I mean it works
But js folks will puke a little in their mouths.
That's not rest. Etc.
João Bragança
@thefringeninja
May 28 2015 14:47
except that is REST. so there
Damian Hickey
@damianh
May 28 2015 14:51
It doesn't matter if you own both the client and server. If this is shipped to other parties as an intergration point, don't do that.
João Bragança
@thefringeninja
May 28 2015 14:52
as long as the client side gest shipped with a Func to correctly construct the content type from the command type is this still an issue?
Damian Hickey
@damianh
May 28 2015 14:53
Potentially. Will the client side be .net?
João Bragança
@thefringeninja
May 28 2015 14:54
for now? sure
i don't see why we can't ship client libraries in other languages
and do the same thing there
Damian Hickey
@damianh
May 28 2015 14:55
The API you ship is HTTP. Any client libs also shipped should only ever be seen as a convenience .
You'll be in a better place long term with that philosophy.
Are you going to write those client libs in other langs and maintain them for all time? Ok, fair play.
imho: client libs should always be seen as optional. HTTP API should be the primary doc'd api.
João Bragança
@thefringeninja
May 28 2015 14:58
again as long as we can generate the documentation why would this be an issue