Joshua Hesketh writes:
> We could then use either psuedo folders[0] or have the worker generate
> an index. For example, why not create an index object with links to
> the other objects (using the known serving application URL prepended)?
> In fact, the reporter can choose whether to generate an
Thierry Carrez writes:
> Joshua Hesketh wrote:
>> Great overview and plan James, thanks for that :-).
>>
>> So it seems to me that we're duplicating the job of swift a little bit
>> by writing a program to accept an object over http and store it on disk.
>> If our end-game is logs stored in swif
On 12 Sep 2013, at 11:51, Thierry Carrez wrote:
>
> That said I agree that reinventing HTTP POST storage sounds overkill and
> storing directly to swift would be a lot simpler.
+2
> Does Swift include
> complex access rules that we could leverage to implement the same kind
> of security that J
Joshua Hesketh wrote:
> Great overview and plan James, thanks for that :-).
>
> So it seems to me that we're duplicating the job of swift a little bit
> by writing a program to accept an object over http and store it on disk.
> If our end-game is logs stored in swift then why not make jenkins (and
