Hmm well my understanding is that the file upload stuff expects
multipart-MIME content type; in fact it explicitly does based on my
recollection of the source. It's certainly possible, I guess, to
create a web service protocol that expects multipart-MIME inputs but
that makes life on the client end a little more of a pain (barring the
existence of a common tool I'm not aware of, and you'd be surprised
how unaware I can be :)
What I'm imagining is a service that expects:
[ Authentication Header ]
[ Content ]
The content would be XML, or a CSV file, or whatever, and it coupled
with the URL determines what the API means.
--
Turtle, turtle, on the ground,
Pink and shiny, turn around.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
