> So, let me clarify this, you want to upload files with a header, is > that about the gist of it? And in this header is some authentication > information? > > How does a classic, multipart/form-data format not work for this case? > > Or do you want the filter to introspect the payload to work out the > authentication details?
Yup that's it. Multipart-MIME would indeed work, but it's marginally more difficult to create the inputs than a format that allows a canned header (kept at the client end of course) to be prepended to an XML or CSV or JSON or whatever blob of content. My experience with typical customer IT departments has led me to believe that even the most trivial of tasks can pose a monumental problem for some customers, so the simpler the better. That aside, as I've pondered this further today I think that it's not really a worthwhile approach, and this is possibly what Oscar was getting at: what I'm trying to avoid is duplication of functionality between services offered via a web UI and services offered through scriptable web-based APIs. My scheme here really wouldn't achieve that at all, without a much more elaborate preprocessing mechanism. Thus, thanks for indulging my out-loud thought process. I'll keep an eye out for anything I see that's similar; I've worked with APIs like this but I've not done much research. -- 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
