[Seaside] Why could a POST take too much?
philippe.marschall at gmail.com
Mon May 12 20:25:10 UTC 2014
On Mon, May 12, 2014 at 10:17 PM, Mariano Martinez Peck
<marianopeck at gmail.com> wrote:
> On Sat, May 10, 2014 at 3:51 AM, Johan Brichau <johan at inceptive.be> wrote:
>> Hi Mariano,
>> I’m afraid you will need to give a bit more info here…
>> Is it a GLASS or Pharo-based application?
> Sorry, I didn't give too much info. It is GLASS.
>> Are you logging the browser response time or is this server-side rendering
>> timing? What is the code, etc… ?
> I am using the developer tools. I attach 2 screenshots, one POST (normal
> one) takes 246ms and the slow one that takes 1.66 seconds in this example.
> Both "submits" were just a click in a menu button.
> The menu is renderrd like this:
> renderActivityMenuOn: html id: anId
> (self showActivityMenu and: [self activityMenu isEmpty not]) ifTrue: [
> html div id:'activityMenuDiv'; with: [
> html form: [
> id: anId;
> with: [
> self activityMenu
> do: [ :menuAction |
> html space.
> beActiveIf: ((menuAction = selectedActivityMenuAction) or:
> [selectedActivityMenuAction isNil and: [self activityMenu first =
> menuAction]]) ;
> callback: [menuAction logAndValue: self.
> selectedActivityMenuAction := menuAction];
> with: [ html text: menuAction label ] ] ] ]]]
> So basically it is a form and each menu item is a button.
> I don't understand why a POST could take 200ms for one menu item and 1.6
> second for another one.
> Any idea? how can I debug it?
The POST is the callback processing, not the rendering. What do you do
More information about the seaside