PDA

View Full Version : Incoming Session Issue



John Hulsman
22-Mar-2007, 12:28 PM
I've got my first self-made AJAX app using the library and hitting some of
my own data going now. I followed Vincent's tutorial. However, I seem to
be having the same issue that MK did in his post labeled "ajax samples". Is
it because there is a Session Manager web object, Web Service web object,
and Web App web object all running at the same time? MK's post got a few
different answers about how this is happing for someone, but then someone
else says it isn't doing it for them and that maybe its just the way they
are doing it. I followed by example. Can someone explain what is doing
this please?

Thanks!

Vincent Oorsprong
22-Mar-2007, 01:03 PM
John,

It is the debugger.

When you run a (AJAX) Web application from the Studio the debugger functions
as webappserver (when you start WebApp Administrator tool you will not see
any sessions and processes started while this would happen when you don't
use the debugger and just start the app from the browser address line).

The AJAX OrderEntry sample application uses a combination of ASP and AJAX
calls (via Javascript). ASP calls are handled by the ASP endpoint interface
of the WebAppServer and AJAX (webservice) calls are handled by the
WebService Endpoint interface. Each endpoint interface starts/uses its own
webapp.exe.

Where WebAppServer can handle numerous concurrent requests from webbrowsers
the debugger can only handle one at the time. So when the ASP file is loaded
the debugger reacts on ASP based calls. When in the middle of handling these
calls a webservice (AJAX) call is retrieved you will be asked if you want to
switch to the incoming request. If you click yes and not all of the ASP
calls are finished you probably end up with a HTTP 404 error. If you reject
the incoming request during the ASP handling you will miss some
functionality.

At this moment there is not a solution for this "feature". We are studying
how to deal with this but don't expect a solution soon. In a NON AJAX
application the incoming request call is usually from a real different
application/user.

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl

John Hulsman
22-Mar-2007, 01:19 PM
Very good. Was just making sure things are as they should be. I'm still
new at this and just wanted to make sure it wasn't something in particular
that I was doing that was causing it.

"Vincent Oorsprong" <vincent.oorsprong@reply.at.newsgroup.nl> wrote in
message news:e3SbrxKbHHA.5152@dacmail.dataaccess.com...
> John,
>
> It is the debugger.
>
> When you run a (AJAX) Web application from the Studio the debugger
> functions as webappserver (when you start WebApp Administrator tool you
> will not see any sessions and processes started while this would happen
> when you don't use the debugger and just start the app from the browser
> address line).
>
> The AJAX OrderEntry sample application uses a combination of ASP and AJAX
> calls (via Javascript). ASP calls are handled by the ASP endpoint
> interface of the WebAppServer and AJAX (webservice) calls are handled by
> the WebService Endpoint interface. Each endpoint interface starts/uses its
> own webapp.exe.
>
> Where WebAppServer can handle numerous concurrent requests from
> webbrowsers the debugger can only handle one at the time. So when the ASP
> file is loaded the debugger reacts on ASP based calls. When in the middle
> of handling these calls a webservice (AJAX) call is retrieved you will be
> asked if you want to switch to the incoming request. If you click yes and
> not all of the ASP calls are finished you probably end up with a HTTP 404
> error. If you reject the incoming request during the ASP handling you will
> miss some functionality.
>
> At this moment there is not a solution for this "feature". We are studying
> how to deal with this but don't expect a solution soon. In a NON AJAX
> application the incoming request call is usually from a real different
> application/user.
>
> --
> Regards,
> Vincent Oorsprong
> Data Access Europe B.V.
> http://www.dataaccess.nl
>