[prev in list] [next in list] [prev in thread] [next in thread]
List: gallery-devel
Subject: [Gallery-devel] Remote API comment
From: Tim Almdal <tnalmdal () shaw ! ca>
Date: 2009-12-29 19:29:35
Message-ID: d156ef63cbcd.4b39e81f () shaw ! ca
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Serge D=3A
Hi=2C I was going over your recent changes to the document and want to m=
ake a few suggestions if possible=2E
I am trying to see how would it fit within this=3A
http=3A//www=2Epicnik=2Ecom/info/api/tutorials/getting-images-out
http=3A//www=2Epicnik=2Ecom/info/api/tutorials/sending-images-in
a) can we make available calls like these which protects and encapsulate=
s API key without HEADER info being used
Get image for edit (HTTP GET)=3A
=A0=A0/index=2Ephp/rest/gallery/API=5FKEY/get/image=2Ejpg
Send image back into gallery (HTTP POST)=3A
=A0=A0/index=2Ephp/rest/gallery/API=5FKEY/put/ - =A0for update
=A0=A0/index=2Ephp/rest/gallery/API=5FKEY/post/ - for new
=A0=A0/index=2Ephp/rest/gallery/API=5FKEY/delete/ - for delete
b) in case of Picnik API we need an ability to hook into incomming strea=
m to process request data (see =22sending-images-in=22 above)
I don=27t see this being an API that meets the needs of every remote sys=
tem out there=2E =A0Nor=2C am I willing to try=2E =A0The proper way to d=
o this is create -contrib module that extends this approach and tailors =
it to the Picnik=27s interface=2E =A0Or Picnik creates a client that use=
s our protocol to extract or loads an image=2E
The big mistake that was made with G2=2C was that it tried to be everyth=
ing to everybody=2E =A0In G3=2C we are not going to try to everything to=
everybody=3B and as such=2C we are depending on the community to add th=
e esoteric functionality that addresses issues such as Picnik interface=2E=
Tim
Website=3A http=3A//www=2Etimalmdal=2Ecom
[Attachment #5 (text/html)]
<div>Serge D:</div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 \
40px; border: none; padding: 0px;"><div>Hi, I was going over your recent changes to \
the document and want to make a few suggestions if possible.</div><div>I am trying to \
see how would it fit within \
this:</div><div>http://www.picnik.com/info/api/tutorials/getting-images-out</div><div> \
http://www.picnik.com/info/api/tutorials/sending-images-in</div><div><br></div><div>a) \
can we make available calls like these which protects and encapsulates API key \
without HEADER info being used</div><div><br></div><div>Get image for edit (HTTP \
GET):</div><div> /index.php/rest/gallery/API_KEY/get/image.jpg</div><div>Send \
image back into gallery (HTTP \
POST):</div><div> /index.php/rest/gallery/API_KEY/put/ - for \
update</div><div> /index.php/rest/gallery/API_KEY/post/ - for \
new</div><div> /index.php/rest/gallery/API_KEY/delete/ - for \
delete</div><div><br></div><div>b) in case of Picnik API we need an ability to hook \
into incomming stream to process request data (see "sending-images-in" \
above)</div></blockquote><div><br></div><div>I don't see this being an API that meets \
the needs of every remote system out there. Nor, am I willing to try. The \
proper way to do this is create -contrib module that extends this approach and \
tailors it to the Picnik's interface. Or Picnik creates a client that uses our \
protocol to extract or loads an image.</div><div><br></div><div>The big mistake that \
was made with G2, was that it tried to be everything to everybody. In G3, we \
are not going to try to everything to everybody; and as such, we are depending on the \
community to add the esoteric functionality that addresses issues such as Picnik \
interface.</div><div><br></div><div>Tim</div><br> Website: \
http://www.timalmdal.com<br><br>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic