Greg, I think this can be helpful. Just to make sure I understand your point; do you mean - give some ID to request on the flask side or before sending request to flask i.e. on Jetty side? Sorry for so trivial question but I have just started learning this hence is a request for clarification.
Best, Aniruddha ======== ᐧ On Sun, Jun 27, 2021 at 7:03 PM Greg Wilkins <gr...@webtide.com> wrote: > Aniruddha, > > sorry, but I have no knowledge of the s3 APIs etc. All I'd say is that > from an async API design point of view, there should always be some > mechanism to allow you to associate an async response received with the > request that you sent. There has got to be a way to either give some ID > or get some ID to the request to Flask is obtainable from the results of > the POST. > > > > > > On Mon, 28 Jun 2021 at 11:52, Aniruddha Tekade via jetty-users < > jetty-users@eclipse.org> wrote: > >> Bill, >> >> Flask server only executes the lambda function (transforming the data -- >> ex. "my experiment with s3 object lambda".upper()) in python and then >> returns (or calls with) the transformed data in the body of response to >> write_get_object_response() defined with Java Server. >> Best, >> Aniruddha >> ======== >> >> ᐧ >> >> On Sun, Jun 27, 2021 at 6:33 PM Bill Ross <r...@cgl.ucsf.edu> wrote: >> >>> If the Flask server doesn't do synchronous responses, that would explain >>> my confusion. If it does, you may be misunderstanding me. >>> >>> Bill >>> On 6/27/21 5:59 PM, Aniruddha Tekade via jetty-users wrote: >>> >>> Yes, I can remove the flask server and use Jython instead to make this >>> run in the same Java server. >>> But since I am trying to reproduce what AWS does with S3 Object Lambda >>> <https://docs.aws.amazon.com/AmazonS3/latest/API/API_WriteGetObjectResponse.html> >>> - >>> >>> *WriteGetObjectResponse* >>>> >>>> <https://docs.aws.amazon.com/AmazonS3/latest/API/s3-api.pdf#API_WriteGetObjectResponse>Passes >>>> transformed objects to a GetObject operation when using Object Lambda >>>> Access Points. For information about Object Lambda Access Points, see >>>> Transforming >>>> objects with Object Lambda Access Points >>>> <https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html> >>>> in >>>> the *Amazon S3 User Guide*. >>>> This operation supports metadata that can be returned by GetObject >>>> <https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html>, >>>> in addition to RequestRoute, RequestToken, StatusCode, ErrorCode, and >>>> ErrorMessage. The GetObject response metadata is supported so that the >>>> WriteGetObjectResponse caller, typically an AWS Lambda function, can >>>> provide the same metadata when it internally invokes GetObject. When >>>> WriteGetObjectResponse is called by a customer-owned Lambda function, >>>> the metadata returned to the end user GetObject call might differ from >>>> what Amazon S3 would normally return. >>> >>> I am trying to find a workaround/mechanism to get this to work. >>> >>> Best, >>> Aniruddha >>> ======== >>> >>> ᐧ >>> >>> On Sun, Jun 27, 2021 at 5:52 PM Bill Ross <r...@cgl.ucsf.edu> wrote: >>> >>>> Speaking from general server dev going back to the 90's, but w/o Amazon >>>> or Flask, so may not apply: >>>> >>>> >>>> - Jetty server now forwards the request to a Python Flask server >>>> which has the lambda function by passing object data to it >>>> - Lambda function code perform the transformation on the object and >>>> POST it back to Jetty server (which is a different API called >>>> writeGetObjectResponse) >>>> >>>> It seems the original GET should be waiting on a synchronous call to >>>> the Flask server (after the sync GET to HS/HSC), and respond by forwarding >>>> the response? >>>> >>>> >>>> >>>> -- >>>> Phobrain.com >>>> _______________________________________________ >>>> jetty-users mailing list >>>> jetty-users@eclipse.org >>>> To unsubscribe from this list, visit >>>> https://www.eclipse.org/mailman/listinfo/jetty-users >>>> >>> >>> _______________________________________________ >>> jetty-users mailing listjetty-us...@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/jetty-users >>> >>> -- >>> Phobrain.com >>> _______________________________________________ >>> jetty-users mailing list >>> jetty-users@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/jetty-users >>> >> _______________________________________________ >> jetty-users mailing list >> jetty-users@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users >> > > > -- > Greg Wilkins <gr...@webtide.com> CTO http://webtide.com >
_______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
