Is it possible to combine AJAX (client-side) with AXIS (server-side)

Discussion:

Ajay Garg

2013-08-11 05:09:38 UTC

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

Rajika Kumarasiri

2013-08-11 22:07:42 UTC

Permalink

Axis2/C is a SOAP engine and it can process a SOAP request that comes from
any kind of client.

Rajika

Post by Ajay Garg
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

Ajay Garg

2013-08-12 05:13:11 UTC

Permalink

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 <

Post by Rajika Kumarasiri
Axis2/C is a SOAP engine and it can process a SOAP request that comes from
any kind of client.
Rajika

--
Regards,
Ajay

Ajay Garg

2013-08-13 14:12:32 UTC

Permalink

Ping !! :)

Post by Ajay Garg
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 :)
===========================
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 <

Post by Rajika Kumarasiri
Axis2/C is a SOAP engine and it can process a SOAP request that comes
from any kind of client.
Rajika

--
Regards,
Ajay

A***@public.gmane.org

2013-08-13 14:20:45 UTC

Permalink

Hi Ajay

As far as I understand, that depends on how you setup your server:

If you are using the simple-httpd Server that comes with axis2/c, I think that is normally sequentially.
But you can also set it up inside an apache server - where again it depents on how you setup your apache - both concurrent threads (with shared global memory) as well as processes (with separate memory) is possible.

Regards
Andreas

________________________________
Von: Ajay Garg [mailto:ajaygargnsit-***@public.gmane.org]
Gesendet: Montag, 12. August 2013 07:13
An: Apache AXIS C User List
Betreff: Re: Is it possible to combine AJAX (client-side) with AXIS (server-side)

Thanks Rajika for the reply.

It seems from http://stackoverflow.com/questions/16534963/ajax-axis2-communication-issue that 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 <***@gmail.com<mailto:rajika.kumarasiri-***@public.gmane.org>> 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 <ajaygargnsit-***@public.gmane.org<mailto:ajaygargnsit-***@public.gmane.org>> 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

Ajay Garg

2013-08-13 14:25:54 UTC

Permalink

Hmm..
Ok, thanks !!

Thanks a ton for the clarification !!!

Post by A***@public.gmane.org
**
Hi Ajay
If you are using the simple-httpd Server that comes with axis2/c, I think
that is normally sequentially.
But you can also set it up inside an apache server - where again it
depents on how you setup your apache - both concurrent threads (with shared
global memory) as well as processes (with separate memory) is possible.
Regards
Andreas
------------------------------
*Gesendet:* Montag, 12. August 2013 07:13
*An:* Apache AXIS C User List
*Betreff:* Re: Is it possible to combine AJAX (client-side) with AXIS
(server-side)
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 :)
===========================
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 <

Post by Rajika Kumarasiri
Axis2/C is a SOAP engine and it can process a SOAP request that comes
from any kind of client.
Rajika

--
Regards,
Ajay

Rajika Kumarasiri

2013-08-13 15:17:14 UTC

Permalink

This would be the correct explanation.

Rajika

Post by Rajika Kumarasiri
Axis2/C is a SOAP engine and it can process a SOAP request that comes
from any kind of client.
Rajika

--
Regards,
Ajay

Thomas Gentsch

2013-08-14 09:30:00 UTC

Permalink

Perhaps it is possible to build it as single-threaded but normally also
the built-in simple http server is multi-threaded.
Just for completeness ... :-)
Rgds
tge

Post by A***@public.gmane.org
Hi Ajay
If you are using the simple-httpd Server that comes with axis2/c, I
think that is normally sequentially.
But you can also set it up inside an apache server - where again it
depents on how you setup your apache - both concurrent threads (with
shared global memory) as well as processes (with separate memory) is
possible.
Regards
Andreas
______________________________________________________________
Gesendet: Montag, 12. August 2013 07:13
An: Apache AXIS C User List
Betreff: Re: Is it possible to combine AJAX (client-side) with
AXIS (server-side)
Thanks Rajika for the reply.
It seems from
http://stackoverflow.com/questions/16534963/ajax-axis2-communication-issue that using it with AJAX might indeed be possible :)
===========================
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
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
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

Ajay Garg

2013-08-14 09:34:34 UTC

Permalink

Thomas,
well.. your reply is in kinda contradiction with others' replies (no
offense intended for anyone) :P

You mean, that if multiple clients happen to hit at a remote call (on the
http_server) at the same time, each call will be served in a dedicated
thread?

Post by Thomas Gentsch
Perhaps it is possible to build it as single-threaded but normally also
the built-in simple http server is multi-threaded.
Just for completeness ... :-)
Rgds
tge

http://stackoverflow.com/questions/16534963/ajax-axis2-communication-issuethat using it with AJAX might indeed be possible :)

Post by A***@public.gmane.org
===========================
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
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
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

---------------------------------------------------------------------

--
Regards,
Ajay

Thomas Gentsch

2013-08-15 19:34:59 UTC

Permalink

Post by Ajay Garg
Thomas,
well.. your reply is in kinda contradiction with others' replies (no
offense intended for anyone) :P
You mean, that if multiple clients happen to hit at a remote call (on
the http_server) at the same time, each call will be served in a
dedicated thread?

Well, that's my observation. You can see that nicely on Linux using gdb:

$ gdb server
(gdb) r
Starting program: server
[Thread debugging using libthread_db enabled]
...
[New Thread 0xb5a13b70 (LWP 21189)]
[Thread 0xb5a13b70 (LWP 21189) exited]
[New Thread 0xb5a13b70 (LWP 21190)]
[New Thread 0xb5212b70 (LWP 21191)]
[New Thread 0xb4a11b70 (LWP 21192)]
[New Thread 0xb4210b70 (LWP 21193)]
[Thread 0xb5a13b70 (LWP 21190) exited]
[Thread 0xb4a11b70 (LWP 21192) exited]
[Thread 0xb5212b70 (LWP 21191) exited]
[Thread 0xb4210b70 (LWP 21193) exited]
[New Thread 0xb4210b70 (LWP 21194)]
[New Thread 0xb5212b70 (LWP 21195)]
[Thread 0xb4210b70 (LWP 21194) exited]
[Thread 0xb5212b70 (LWP 21195) exited]
[New Thread 0xb4a11b70 (LWP 21196)]
...

Happens whenever a client sends a request, in the example above I
started multiple in parallel.

Regards
tge

Post by Ajay Garg
Perhaps it is possible to build it as single-threaded but normally also
the built-in simple http server is multi-threaded.
Just for completeness ... :-)
Rgds
tge
On Tue, 2013-08-13 at 14:20 +0000,

Post by A***@public.gmane.org
Hi Ajay
As far as I understand, that depends on how you setup your
If you are using the simple-httpd Server that comes with

axis2/c, I

Post by A***@public.gmane.org
think that is normally sequentially.
But you can also set it up inside an apache server - where

again it

Post by A***@public.gmane.org
depents on how you setup your apache - both concurrent

threads (with

Post by A***@public.gmane.org
shared global memory) as well as processes (with separate

memory) is

Post by A***@public.gmane.org
possible.
Regards
Andreas

______________________________________________________________

Post by A***@public.gmane.org
Gesendet: Montag, 12. August 2013 07:13
An: Apache AXIS C User List
Betreff: Re: Is it possible to combine AJAX

(client-side) with

Post by A***@public.gmane.org
AXIS (server-side)
Thanks Rajika for the reply.
It seems from

http://stackoverflow.com/questions/16534963/ajax-axis2-communication-issue that using it with AJAX might indeed be possible :)

Post by A***@public.gmane.org
===========================
Let's say "n" clients hit upon one same

remote-API-call on

Post by A***@public.gmane.org
AXIS2/C.
Will each of these client-requests be
* served in individual dedicated "thread"s,

meaning that

Post by A***@public.gmane.org
there might be concurrency benefits?
(as it happens in servlets running in

Apache-Tomcat)

Post by A***@public.gmane.org
* served in a single thread, sequentially?

(i.e. first

Post by A***@public.gmane.org
client "1" is served, then client "2", and so

on ...)

Post by A***@public.gmane.org
(as it happens in server-side Node.js)
* served in a dedicated "process", meaning that

there

Post by A***@public.gmane.org
might be concurrency benefits (but of course, with

the caveats

Post by A***@public.gmane.org
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
Axis2/C is a SOAP engine and it can process

a SOAP

Post by A***@public.gmane.org
request that comes from any kind of client.
Rajika
On Sun, Aug 11, 2013 at 1:09 AM, Ajay Garg
Hi all.
I have been evaluating various

options for a

Post by A***@public.gmane.org
web-framework for simple passing of

data-lists

Post by A***@public.gmane.org
between clients and server, via

HTTP.

Post by A***@public.gmane.org
In this regard, combining AJAX and

AXIS (with

Post by A***@public.gmane.org
SOAP) would be the ideal scenario

for me.

Post by A***@public.gmane.org
Is it possible? If yes, is it

recommended to

Post by A***@public.gmane.org
combine these two technologies (as

far as

Post by A***@public.gmane.org
reliability is concerned)?
I will be grateful for any

pointers :)

Post by A***@public.gmane.org
Regards,
Ajay
--
Regards,
Ajay

---------------------------------------------------------------------
--
Regards,
Ajay