Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

parallel execution of application

Inactive

Description

Hello everyone,

Currently I am working on a solution where I have to call a common application from more than one  applications and for every call, a new instance of a common application should be execute as shown in following picture.

Here I am calling App C from App A and App B using afb_api_call_sync() function but App C execute every call in synchronous manner. I want app c to be execute each call in new instance of App C.

Que:  Is there any function/API available in AGL which call the application and execute in new instance for each application call?

Environment

None

Attachments

5

Activity

Show:

Walt Miner 
May 10, 2023 at 8:37 PM

  Can this be resolved?

jose bollo 
February 24, 2023 at 4:43 PM

I have to postpone further look to next week ...

shubham kadu 
February 23, 2023 at 4:38 PM

Hello Jose,

I am currently using Lamprey and thank you for your suggestion I will add it in bindings.

jose bollo 
February 23, 2023 at 3:45 PM

I agree that there is an issue and that the server is not scheduling the requests in parallele.

What is the used version?

NB: you should add "afb_req_reply(req,response,NULL,NULL);" in one/two-binding.c otherwise you get an error.

shubham kadu 
February 23, 2023 at 12:33 PM

Hello,

As Scott mention, All three apps are actually binding files written in c.  I have written a sample code (attached below). In that code I tried to call "ping"  verb of  server_binding.c form one_binding.c and two_binding.c respectively. You can see that the run function of server doing some iteration and after that it is giving reply back to calling API. I have also attached snapshot of log there you can see that server is executing call from binding one and then from binding two synchronously.

But my expectation is that both call from one_binding.c and two_binding.c should be execute parallelly.  Is there any AGL function able to do this?

Details

Assignee

Reporter

Labels

Hardware Platform(s) Affected

QEMU ARM
QEMU ARM 64
QEMU x86_64

Components

Affects versions

Due date

Priority

Created February 7, 2023 at 5:45 AM
Updated June 21, 2023 at 3:06 PM
Resolved June 21, 2023 at 3:06 PM