Hey Michael,
The doodle3d API looks pretty cool - I actually hadn't seen this one
before. Here's my take:
good
- in active development (Tegh is no longer being developed unfortunately
- I've stopped development to focus on my day job)
- restful (simple, stateless, web and mobile devs are already familiar
with it)
- simpler JSON payloads then Tegh (less nested JSON)
- no need for broadcast-based service discovery (ie. mdns or upnp which
in my experience less developers are familiar with)
- has an API for printer configuration (Tegh did not)
- compatible with tons of 3D printers
bad
- centralized/needs to be connected to the internet (depends on
http://connect.doodle3d.com/api/ for printer discovery)
- only supports a single hotend/extruder (AFAIK?)
- larger json payloads for status polling (compared to Tegh change
events)
- no websocket or long polling api => no realtime events (developers
have to implement ajax polling if they want something approximately the
same however it's generally less efficient and in my experience a good way
to kill cellphone batteries really quickly)
Cheers,
Rob
On Sun, Jan 4, 2015 at 9:58 AM, Michael Sweet <msweet at apple.com> wrote:
> All,
>> Saw this 3D printer accessory while browsing today...
>>http://www.doodle3d.com/help/api-documentation <
>http://www.doodle3d.com/help/api-documentation>
>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> _______________________________________________
> 3d-printing mailing list
>3d-printing at pwg.org>https://www.pwg.org/mailman/listinfo/3d-printing>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/3d-printing/attachments/20150104/81b0bd5b/attachment.html>