Comments for .zugiart

Comment on Stateful & standalone apache XML-RPC server by zen

zen — Sat, 04 Feb 2012 08:14:00 +0000

have you tried using synchronized keyword?
let’s say, the stack is like this

xmlrpcClient xmlrpcServer FOO(withNonThreadSafeConns) other servers.

You are right, the key is then to control no two threads of execution uses FOO and the resources within it at the same time. If that is true, the synchronized keyword might be enough (I don’t know what your scenario is). Basically FOO needs to wrap around the non-threadsafe resources and ensures that when clients of FOO calls its methods/services, it does so in a thread-safe way.

You can try: Ihttp://www.google.co.com/search?q=synchronized+keyword for synchronized keyword in java.

If this won’t do, and you think you want to use a request queue. The queue mechanism itself must be threadsafe, and it also need to be blocking. the flow then becomes:

client xmlrpcserver queue FOO servers

1. client(s) call server
2. server receive request, put request in the queue and blocks the thread of execution until a the result is processed by FOO.
3. once result is received by server, returns result back to client.

the blocking part is important because RPC is a synchronous style operation. It is not event-style operation.

good luck!

Comment on Stateful & standalone apache XML-RPC server by Ctgaurav

Ctgaurav — Sat, 04 Feb 2012 07:37:00 +0000

Hi want add a functionality to my XML RPC server , Server uses a set of connections to other servers and connections are non serilizable and not thread safe , so to process request of multiple clients at same time problem comes at a time connection used just for one client , i want to aad a request queue and response queue for clients …how i acn implement this ..what is better way to acomplish this

Comment on zroundup, a demo by Anonymous

Anonymous — Wed, 25 Jan 2012 01:52:00 +0000

This was a while back! Yes I did, but didn’t have time to push it all the way as a proper product. I used the demo script as a template and modified it from there. I did managed to get it fit into the USB stick, which is ultra portable but the performance is slow as. I thought it’ll be better if I could make some program to copy it into a temp folder in the C: drive and upon closure copies the data back to USB. But I never finished it to that point.

I’d love to have more spare time to continue it though. Atm an instance of this is running locally in my home to manage my life task. Python Roundup is very versatile and flexible, I loved it.

Comment on zroundup, a demo by interestedparty

interestedparty — Wed, 25 Jan 2012 01:11:00 +0000

Hi,

Did you ever get it to work as zero config?

Comment on Java: Date, ISO string, and timezone by Balu

Balu — Sat, 31 Dec 2011 10:59:24 +0000

Hey AB.. thanks a lot… its solved my issue.

Comment on The Ten Factors by Siddharth

Siddharth — Sat, 17 Dec 2011 19:12:23 +0000

Thank you very much!! I love the way you explained everything pictorially! Maybe you can also talk about consistency from the beginning to the end

Comment on Stateful & standalone apache XML-RPC server by zen

zen — Wed, 26 Oct 2011 08:11:24 +0000

@ben, ah thats what you mean. So yeah in short if you use the above snippets, you do have to make your handler object thread-safe. Try this: http://www.google.com/search?q=java+thread+safe

Comment on Stateful & standalone apache XML-RPC server by zen

zen — Wed, 26 Oct 2011 08:09:17 +0000

Hm, I don’t understand your question, sorry – it’s a bit unclear. But the xml rpc library from apache is quite flexible, so the answer is actually “depends on your configuration”. You can have it so that a new handler is created for every request (and every request is a new thread). You can also make it so that the handler gets recycled for all request that asks for handler.methodName() thus allowing the handler to be stateful.

This example uses the same object and reuse it as the handler for each request. In the above example “SimpleXMLRpcTest” – if 3 clients calls zen.hello() at (roughly) the same time, the one object will be accessed concurrently. Therefore if you use my example, and you then share key variables between functions, you have to be careful and handle the concurrent access properly (just use ‘synchronized’ keyword as appropriate).

Comment on Stateful & standalone apache XML-RPC server by Ben

Ben — Wed, 26 Oct 2011 07:55:01 +0000

In apache xmlrpc: what happens if 2 or more clients send a request at the same time? Are they queued? Do I have the guarantee that if two clients call the same or different functions they are executed one after another and not at the same time?

Comment on Stateful & standalone apache XML-RPC server by Ben

Ben — Wed, 26 Oct 2011 07:47:48 +0000

thx for your article! Hey,zen,I wanna ask a question: Does xmlrpc server call multi-threads to cope with the requests from different clients? thats to say: server calls the handler-method one by one request OR server uses multi-threads to call the method to handle different requests from different clients at same time? i really wanna know~pls~~