Re: RPC with LWIP

2014-07-07 Thread Mhamad Hmad
Hi Norman, Thank you for you last email . In the same time i would like to thank Johannes for the great help also. the RPC_LWIP work fine now with out blocking, I did not finish the whole test process yet but till now it is working smoothly . i will keep all in touch in the case of facing troubles

Re: RPC with LWIP

2014-07-07 Thread Johannes Schlatow
Hi Norman, in order to simplify the implementation of multi-threaded/multi-entrypoint servers, I made an attempt to extract the generic part from the multi-threaded timer implementation you referenced. I therefore created a Root_component_multi and a Session_component_multi from which a server im

Re: RPC with LWIP

2014-07-02 Thread Norman Feske
Hi Mohammad, > from the client side i connect to the both server by telent each of > them and type message to them and it work smoothly. > so , I think without using the RPC we dont have the blocking problem or > may be my test was wrong . > i will attach the .run ,server.c and .mk files . your

Re: RPC with LWIP

2014-06-26 Thread Mhamad Hmad
hi Norman , >>As for simplifying the scenario, I recommend you to take the RPC >>interface out for now. Integrate both clients into a single program, >>which also links against lwIP. Create a thread for each client and let >>the thread call the respective "main" routine. When running the >>resulti

Re: RPC with LWIP

2014-06-26 Thread Norman Feske
Hi Mohammad, > thank you for your replay, > Acctually i am thinking in using the second option by making the server > multi-threaded (using one entrypoint per session). but in this case i > am facing the problem that the RPC has its own schedule and the LwIP > also has it is own one too . So in

Re: RPC with LWIP

2014-06-25 Thread Mhamad Hmad
Hi Norman, thank you for your replay, Acctually i am thinking in using the second option by making the server multi-threaded (using one entrypoint per session). but in this case i am facing the problem that the RPC has its own schedule and the LwIP also has it is own one too . So in one case i wi

Re: RPC with LWIP

2014-06-15 Thread Norman Feske
Hi, > *I am little confused . Do i need to change all the liwp socket calls > wich has blocking property like (accept , recvfrom,etc ) with non > blocking calls, then I need to use asynchronous notifications. instead > of using Block RPC calls , * you would still use RPC calls for the those ope

Re: RPC with LWIP

2014-06-05 Thread Mhamad Hmad
*Hi Norman,* *I am little confused . Do i need to change all the liwp socket calls wich has blocking property like (accept , recvfrom,etc ) with non blocking calls, then I need to use asynchronous notifications. instead of using Block RPC calls , * *thanks* 2014-05-28 19:30 GMT+01:00 Norman Fe

Re: RPC with LWIP

2014-05-28 Thread Norman Feske
Hi Mohammad, the steps you described look plausible to me. > What I am Facing: > > - when i tried to run more then one echo server ( in different port) > ,the lwip is > not working will and what i found that when the tow echo server > try to accept > connection the first one will

RPC with LWIP

2014-05-26 Thread Mhamad Hmad
Hi, i will try explain what i want and what i did and then what i am facing, What i am trying to do : - using only one LWIP (tcp-ip) stack - the communication with lwip will be by using RPC calls. - the system should be multi-threading and serve many process in the same