Using concurrent request handling in WebObjects may appear as deceptively
simple as turning on a property...
However, in a real project it'll be a little more involved than that - you do
have to manage shared mutable data and locking/unlocking of EO editing contexts
- to avoid deadlocks - the b
Ok, thanks for your help.
On Jun 3, 2010, at 4:09 AM, Amedeo Mantica wrote:
For some tasks, I would like to split the process in threads by
number of available processors
btw, running more instances is good
Amedeo
On 03/giu/2010, at 01.26, Q wrote:
On 03/06/2010, at 9:15 AM, Miguel Ang
On Jun 3, 2010, at 9:40 AM, Mark Ritchie wrote:
On 3/Jun/2010, at 7:13 AM, Chuck Hill wrote:
Darn, I would have liked to see that!
Perhaps the presenter can be talked into repeating the prezo at
WOWODC? ;-)
M.
But, alas, we don't know the presenters name. ;-)
--
Chuck Hill
On 3/Jun/2010, at 7:13 AM, Chuck Hill wrote:
> Darn, I would have liked to see that!
Perhaps the presenter can be talked into repeating the prezo at WOWODC? ;-)
M.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing
The default port for HTTPS is 443, not 7070.
On Jun 3, 2010, at 10:42 AM, Kalpana Vaka wrote:
> Hi All,
>
> We are trying to deploy our application with SSL configuration (Apache).
>
> We have included the following line in httpd.conf to consider SSL
> configuration.
>
> Include conf/extra
in your VirtualHost config have you set a servername ? or, more to the
point, is it set as localhost ?
On 3 June 2010 15:49, Kalpana Vaka wrote:
> Hi All,
>
>
>
> We are trying to deploy our application (WO-5.4.3) with SSL configuration
> (Apache 2.2).
>
>
>
> We have included the following l
Hi All,
We are trying to deploy our application (WO-5.4.3) with SSL configuration
(Apache 2.2).
We have included the following line in httpd.conf to consider SSL
configuration.
Include conf/extra/httpd-ssl.conf
And we have configured the VirtualHost on port 7070 in httpd-ssl.conf
Hi All,
We are trying to deploy our application with SSL configuration (Apache).
We have included the following line in httpd.conf to consider SSL
configuration.
Include conf/extra/httpd-ssl.conf
And we have configured the VirtualHost on port 7070 in httpd-ssl.conf. And
updated th
How will they be the same or different or ?
This stuff is very relevant and important to me and my clients going forward.
Thanks
James
On Jun 2, 2010, at 6:01 PM, Pascal Robert wrote:
>
> Le 10-06-02 à 18:19, Mark Ritchie a écrit :
>
>> On 2/Jun/2010, at 2:45 PM, David den Boer wrote:
>>>
On Jun 2, 2010, at 2:45 PM, David den Boer wrote:
Be sure to attend Session 117 on Wednesday morning for probably the
only WO mention of the week:
Probably? :-P
Building a Server-driven User Experience
Powerful server-side technologies and Cocoa Touch best practices
make it easy to rem
HI Simon,
On Jun 3, 2010, at 3:28 AM, Simon wrote:
hi all -
we've got a session time-out issue that is affecting just 1 specific
client. all other users of the app are happy - it's just not working
for this one company.
basically, as users form this one company click around the app they
On 3 Jun 2010, at 11:28, Simon wrote:
hi all -
we've got a session time-out issue that is affecting just 1
specific client. all other users of the app are happy - it's just
not working for this one company.
basically, as users form this one company click around the app they
randomly ge
Is it a secured app? Easiest way to cause yourself session weirdness is
mixing HTTPS and HTTP in the wrong places.
Have you traced session creation to see if a second session is in play
or is it just the original session timing out? Firebug/dev tools can be
your friend here too.
On 6/3/10
we store in the url - good point. thanks pascal, will check...
simon
On 3 June 2010 11:48, Pascal Robert wrote:
> Are you storing the session ID in a cookie or in the URL? Maybe the proxy
> is removing the session ID from the URL.
>
> > hi all -
> >
> > we've got a session time-out issue that i
Are you storing the session ID in a cookie or in the URL? Maybe the proxy is
removing the session ID from the URL.
> hi all -
>
> we've got a session time-out issue that is affecting just 1 specific client.
> all other users of the app are happy - it's just not working for this one
> company.
hi all -
we've got a session time-out issue that is affecting just 1 specific client.
all other users of the app are happy - it's just not working for this one
company.
basically, as users form this one company click around the app they randomly
get instant session time-out's. no browser hanging
For some tasks, I would like to split the process in threads by number of
available processors
btw, running more instances is good
Amedeo
On 03/giu/2010, at 01.26, Q wrote:
>
> On 03/06/2010, at 9:15 AM, Miguel Angel Torres Avila wrote:
>
>> Thanks Guido,
>>
>> Ok that advantage is implicit
17 matches
Mail list logo
