Thanks Rajika for the reply.
It seems from
http://stackoverflow.com/questions/16534963/ajax-axis2-communication-issuethat
using it with AJAX might indeed be possible :)
Just one question regarding AXIS2/C ::
===========================
Let's say "n" clients hit upon one same remote-API-call on AXIS2/C.
Will each of these client-requests be
* served in individual dedicated "thread"s, meaning that there might
be concurrency benefits?
(as it happens in servlets running in Apache-Tomcat)
* served in a single thread, sequentially? (i.e. first client "1" is
served, then client "2", and so on ...)
(as it happens in server-side Node.js)
* served in a dedicated "process", meaning that there might be
concurrency benefits (but of course, with the caveats of the "bulkiness"
of a "process")?
(as it happens in server-side PHP)
Thanks again !!!
On Mon, Aug 12, 2013 at 3:37 AM, Rajika Kumarasiri <
rajika.kumaras...@gmail.com> wrote:
> Axis2/C is a SOAP engine and it can process a SOAP request that comes from
> any kind of client.
>
> Rajika
>
>
> On Sun, Aug 11, 2013 at 1:09 AM, Ajay Garg <ajaygargn...@gmail.com> wrote:
>
>> Hi all.
>>
>> I have been evaluating various options for a web-framework for simple
>> passing of data-lists between clients and server, via HTTP.
>> In this regard, combining AJAX and AXIS (with SOAP) would be the ideal
>> scenario for me.
>>
>> Is it possible? If yes, is it recommended to combine these two
>> technologies (as far as reliability is concerned)?
>>
>>
>>
>> I will be grateful for any pointers :)
>>
>>
>>
>> Regards,
>> Ajay
>>
>
>
--
Regards,
Ajay
