[Lift] Re: JQuery corners

[David Pollak]

Alex,

Thanks for taking the time to put together an example of the issue.

I think this whole exchange underscores the value of community.  Alex raised
an issue and spent the time to put together a reproducible example.  Marius,
Xavi, and I worked together to understand the issue and discuss solutions.
The whole community has a better understanding of how Lift works and how to
diagnose issues.

So, thanks to all for going through the cycle.

David

On Sun, Feb 8, 2009 at 8:40 AM, Alex Boisvert  wrote:

> Thanks guys!
>
> Silly me, I was looking at "Show page source" ... should have used
> Firebug.   (There's a lesson for me here)
>
> And thanks for the solution, too.   I would not have easily figured out how
> to work around this situation.
>
> alex
>
> On Sat, Feb 7, 2009 at 9:21 PM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
>> Alex,
>> Using Firebug, I looked at how the library re-wrote the form.  It turned
>> the  into an  tag.  The destruction of
>> the generated submit tag resulted in the function not getting called.
>>
>> I've updated your snippet to work around the jQuery.corners plugin:
>> bind("ts", xhtml,
>>   "entry" -> SHtml.text(entry, entry = _, ("maxlength", "60")),
>>   "submit" -> (SHtml.hidden(add _) ++ > class="rounded {transparent} button" value="Submit"/>))
>>
>> The submit button gets bound to a hidden field and a submit button.  The
>> submit button is safe to re-write because it does nothing on the server
>> side.
>>
>> Thanks,
>>
>> David
>>
>> On Sat, Feb 7, 2009 at 6:25 PM, Alex Boisvert wrote:
>>
>>> Hi David, Marius,
>>>
>>> Here's a small project that illustrates the issue...
>>>
>>> To reproduce,
>>> 1) Unzip corners.zip
>>> 2) Run "mvn jetty:run"
>>> 3) Go to http://localhost:8080
>>> 4) Type something in the text field and click "Submit" button
>>> => You should see "Notice: * You typed: [something]" appear
>>> 5) Edit src/main/webapp/index.html and uncomment this fragment
>>>
>>>   
>>>
>>> 6) Refresh the page
>>> 7) Type something  in the text field and click "Submit" button
>>> => Nothing happens?!?
>>>
>>> Hopefully you'll get the same behavior as I do.
>>>
>>> alex
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Git some: http://github.com/dpp
>>
>>
>>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[David Pollak]

On Sun, Feb 8, 2009 at 7:40 AM, Marius  wrote:

>
> I can make these changes one of these days if it's fine with you.


Please make them as soon as is convenient.  It's time to let the bits sit
prior to 1.0 shipping.


>
>
> On Feb 8, 5:23 pm, David Pollak  wrote:
> > On Sun, Feb 8, 2009 at 12:37 AM, Marius  wrote:
> >
> > > Dave this is way awesome!
> >
> > > I have some questions/suggestions if I may
> >
> > > 1. Currently Lift purges the unseen functions that are older then 10
> > > minutes. I think it might help to make this time window configurable
> > > via LiftRules so that people may adjust it to fit their specific
> > > application needs.
> >
> > Sure.
> >
> >
> >
> > > 2. AddLiftGCToBody should probably not renders anything related with
> > > GC if the GC nodes list is empty? ... or have the ability to disable
> > > the GC support which might be quite handy for mobile web applications
> > > used for limited browsers.
> >
> > Disable GC... cool.  Not sending the Ajax request if the list is empty,
> > cool.  But it's possible that items come onto the page via Ajax or Comet.
> >  Thus, we have to run the node walk as long as GC is enabled.
> >
> >
> >
> > > 3. Lift for every page is starting the JS GC "daemon" that
> > > periodically sends the GC request up (every 75 seconds for success or
> > > 15 seconds for failure). Shouldn't we make these these times intervals
> > > configurable from LiftRules?
> >
> > Sure.
> >
> >
> >
> >
> >
> > > Thoughts?
> >
> > > Br's,
> > > Marius
> >
> > > On Feb 8, 2:05 am, David Pollak  wrote:
> > > > Folks,
> >
> > > > I've found and squashed a bunch of memory retention issues in the
> Lift
> > > comet
> > > > stuff (and added the garbage collection for functions.)
> >
> > > > I've tested the fixes against the livehttp://demo.liftweb.netandthere
> > > has
> > > > been no memory growth (except in Derby, but that's not Lift's
> problem)
> > > for
> > > > 24 hours.
> >
> > > > I've been using YouKit (http://yourkit.com/) to profile that
> > > application.
> > > > I've gotta say that YourKit is awesome, even for debugging remote
> code.
> > >  I'd
> > > > like to thank YourKit again for contributing licenses to the Lift
> > > > committers.
> >
> > > > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > > > practice, the actual heap size for the site never grew beyond about
> 10MB.
> >
> > > > Thanks,
> >
> > > > David
> >
> > > > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
> >
> > > > --
> > > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > > Follow me:http://twitter.com/dpp
> > > > Git some:http://github.com/dpp
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: Is it legal to update a SessionVar in LiftRules.rewrite?

[Alex Boisvert]

Ok, makes sense.   I'll use a RequestVar instead.

thanks!
alex


On Sat, Feb 7, 2009 at 9:07 PM, David Pollak
wrote:

> Alex,
> The session is not in scope during the rewrite phase, so SessionVars are
> not available.  This is because the rewrite happens before dispatching
> begins and dispatching can be done to a stateless/sessionless dispatch.
>
> However, the default value of a SessionVar is not calculated until the
> SessionVar is accessed, so in your example, if you are accessing the
> SessionVar during normal response handling, the statement will evaluate
> correctly.
>
> Hope this helps.
>
> Thanks,
>
> David
>
>
> On Sat, Feb 7, 2009 at 8:44 PM, Alex Boisvert wrote:
>
>> On Sat, Feb 7, 2009 at 6:59 PM, Alex Boisvert wrote:
>>
>>> object Session {
>>>   object foo extends RequestVar[Int](S.param("foo").map(_.toInt) openOr
>>> (1))
>>> }
>>
>>
>> Sorry, I made a typo here.. it should read:
>>
>>   object foo extends SessionVar[Int](S.param("foo").map(_.toInt) openOr
>> (1))
>>  ^^
>>
>> alex
>>
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: JQuery corners

[Alex Boisvert]

Thanks guys!

Silly me, I was looking at "Show page source" ... should have used
Firebug.   (There's a lesson for me here)

And thanks for the solution, too.   I would not have easily figured out how
to work around this situation.

alex

On Sat, Feb 7, 2009 at 9:21 PM, David Pollak
wrote:

> Alex,
> Using Firebug, I looked at how the library re-wrote the form.  It turned
> the  into an  tag.  The destruction of
> the generated submit tag resulted in the function not getting called.
>
> I've updated your snippet to work around the jQuery.corners plugin:
> bind("ts", xhtml,
>   "entry" -> SHtml.text(entry, entry = _, ("maxlength", "60")),
>   "submit" -> (SHtml.hidden(add _) ++  class="rounded {transparent} button" value="Submit"/>))
>
> The submit button gets bound to a hidden field and a submit button.  The
> submit button is safe to re-write because it does nothing on the server
> side.
>
> Thanks,
>
> David
>
> On Sat, Feb 7, 2009 at 6:25 PM, Alex Boisvert wrote:
>
>> Hi David, Marius,
>>
>> Here's a small project that illustrates the issue...
>>
>> To reproduce,
>> 1) Unzip corners.zip
>> 2) Run "mvn jetty:run"
>> 3) Go to http://localhost:8080
>> 4) Type something in the text field and click "Submit" button
>> => You should see "Notice: * You typed: [something]" appear
>> 5) Edit src/main/webapp/index.html and uncomment this fragment
>>
>>   
>>
>> 6) Refresh the page
>> 7) Type something  in the text field and click "Submit" button
>> => Nothing happens?!?
>>
>> Hopefully you'll get the same behavior as I do.
>>
>> alex
>>
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[Marius]

Please ignore this message ... I "removed" it ... I was thinking to
something else which of course clarified for me in the mean time :)

On Feb 8, 5:24 pm, David Pollak  wrote:
> On Sun, Feb 8, 2009 at 5:36 AM, Marius  wrote:
>
> > Related with the above ... would it be ok with you to have a comet
> > long-polling interval configurable from somewhere (i.e LiftRules)? ...
> > currently it is hardcoded to 10 seconds.
>
> The Comet long poll should be restarted 100ms after the last successful long
> poll.  This should not be configurable.  If you don't want long poll, don't
> put Comet components on the page.
>
> I'm cool with configurability of long poll failure timeout.
>
>
>
>
>
> > On Feb 8, 10:37 am, Marius  wrote:
> > > Dave this is way awesome!
>
> > > I have some questions/suggestions if I may
>
> > > 1. Currently Lift purges the unseen functions that are older then 10
> > > minutes. I think it might help to make this time window configurable
> > > via LiftRules so that people may adjust it to fit their specific
> > > application needs.
>
> > > 2. AddLiftGCToBody should probably not renders anything related with
> > > GC if the GC nodes list is empty? ... or have the ability to disable
> > > the GC support which might be quite handy for mobile web applications
> > > used for limited browsers.
>
> > > 3. Lift for every page is starting the JS GC "daemon" that
> > > periodically sends the GC request up (every 75 seconds for success or
> > > 15 seconds for failure). Shouldn't we make these these times intervals
> > > configurable from LiftRules?
>
> > > Thoughts?
>
> > > Br's,
> > > Marius
>
> > > On Feb 8, 2:05 am, David Pollak  wrote:
>
> > > > Folks,
>
> > > > I've found and squashed a bunch of memory retention issues in the Lift
> > comet
> > > > stuff (and added the garbage collection for functions.)
>
> > > > I've tested the fixes against the livehttp://demo.liftweb.netandthere
> > has
> > > > been no memory growth (except in Derby, but that's not Lift's problem)
> > for
> > > > 24 hours.
>
> > > > I've been using YouKit (http://yourkit.com/) to profile that
> > application.
> > > > I've gotta say that YourKit is awesome, even for debugging remote code.
> >  I'd
> > > > like to thank YourKit again for contributing licenses to the Lift
> > > > committers.
>
> > > > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > > > practice, the actual heap size for the site never grew beyond about
> > 10MB.
>
> > > > Thanks,
>
> > > > David
>
> > > > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
>
> > > > --
> > > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > > Follow me:http://twitter.com/dpp
> > > > Git some:http://github.com/dpp
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[Marius]

I can make these changes one of these days if it's fine with you.

On Feb 8, 5:23 pm, David Pollak  wrote:
> On Sun, Feb 8, 2009 at 12:37 AM, Marius  wrote:
>
> > Dave this is way awesome!
>
> > I have some questions/suggestions if I may
>
> > 1. Currently Lift purges the unseen functions that are older then 10
> > minutes. I think it might help to make this time window configurable
> > via LiftRules so that people may adjust it to fit their specific
> > application needs.
>
> Sure.
>
>
>
> > 2. AddLiftGCToBody should probably not renders anything related with
> > GC if the GC nodes list is empty? ... or have the ability to disable
> > the GC support which might be quite handy for mobile web applications
> > used for limited browsers.
>
> Disable GC... cool.  Not sending the Ajax request if the list is empty,
> cool.  But it's possible that items come onto the page via Ajax or Comet.
>  Thus, we have to run the node walk as long as GC is enabled.
>
>
>
> > 3. Lift for every page is starting the JS GC "daemon" that
> > periodically sends the GC request up (every 75 seconds for success or
> > 15 seconds for failure). Shouldn't we make these these times intervals
> > configurable from LiftRules?
>
> Sure.
>
>
>
>
>
> > Thoughts?
>
> > Br's,
> > Marius
>
> > On Feb 8, 2:05 am, David Pollak  wrote:
> > > Folks,
>
> > > I've found and squashed a bunch of memory retention issues in the Lift
> > comet
> > > stuff (and added the garbage collection for functions.)
>
> > > I've tested the fixes against the livehttp://demo.liftweb.netandthere
> > has
> > > been no memory growth (except in Derby, but that's not Lift's problem)
> > for
> > > 24 hours.
>
> > > I've been using YouKit (http://yourkit.com/) to profile that
> > application.
> > > I've gotta say that YourKit is awesome, even for debugging remote code.
> >  I'd
> > > like to thank YourKit again for contributing licenses to the Lift
> > > committers.
>
> > > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > > practice, the actual heap size for the site never grew beyond about 10MB.
>
> > > Thanks,
>
> > > David
>
> > > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
>
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[David Pollak]

On Sun, Feb 8, 2009 at 5:36 AM, Marius  wrote:

>
> Related with the above ... would it be ok with you to have a comet
> long-polling interval configurable from somewhere (i.e LiftRules)? ...
> currently it is hardcoded to 10 seconds.


The Comet long poll should be restarted 100ms after the last successful long
poll.  This should not be configurable.  If you don't want long poll, don't
put Comet components on the page.

I'm cool with configurability of long poll failure timeout.


>
>
> On Feb 8, 10:37 am, Marius  wrote:
> > Dave this is way awesome!
> >
> > I have some questions/suggestions if I may
> >
> > 1. Currently Lift purges the unseen functions that are older then 10
> > minutes. I think it might help to make this time window configurable
> > via LiftRules so that people may adjust it to fit their specific
> > application needs.
> >
> > 2. AddLiftGCToBody should probably not renders anything related with
> > GC if the GC nodes list is empty? ... or have the ability to disable
> > the GC support which might be quite handy for mobile web applications
> > used for limited browsers.
> >
> > 3. Lift for every page is starting the JS GC "daemon" that
> > periodically sends the GC request up (every 75 seconds for success or
> > 15 seconds for failure). Shouldn't we make these these times intervals
> > configurable from LiftRules?
> >
> > Thoughts?
> >
> > Br's,
> > Marius
> >
> > On Feb 8, 2:05 am, David Pollak  wrote:
> >
> > > Folks,
> >
> > > I've found and squashed a bunch of memory retention issues in the Lift
> comet
> > > stuff (and added the garbage collection for functions.)
> >
> > > I've tested the fixes against the livehttp://demo.liftweb.netandthere
> has
> > > been no memory growth (except in Derby, but that's not Lift's problem)
> for
> > > 24 hours.
> >
> > > I've been using YouKit (http://yourkit.com/) to profile that
> application.
> > > I've gotta say that YourKit is awesome, even for debugging remote code.
>  I'd
> > > like to thank YourKit again for contributing licenses to the Lift
> > > committers.
> >
> > > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > > practice, the actual heap size for the site never grew beyond about
> 10MB.
> >
> > > Thanks,
> >
> > > David
> >
> > > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
> >
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[David Pollak]

On Sun, Feb 8, 2009 at 12:37 AM, Marius  wrote:

>
> Dave this is way awesome!
>
> I have some questions/suggestions if I may
>
>
> 1. Currently Lift purges the unseen functions that are older then 10
> minutes. I think it might help to make this time window configurable
> via LiftRules so that people may adjust it to fit their specific
> application needs.


Sure.


>
>
> 2. AddLiftGCToBody should probably not renders anything related with
> GC if the GC nodes list is empty? ... or have the ability to disable
> the GC support which might be quite handy for mobile web applications
> used for limited browsers.
>

Disable GC... cool.  Not sending the Ajax request if the list is empty,
cool.  But it's possible that items come onto the page via Ajax or Comet.
 Thus, we have to run the node walk as long as GC is enabled.

>
> 3. Lift for every page is starting the JS GC "daemon" that
> periodically sends the GC request up (every 75 seconds for success or
> 15 seconds for failure). Shouldn't we make these these times intervals
> configurable from LiftRules?
>

Sure.


>
> Thoughts?
>
> Br's,
> Marius
>
> On Feb 8, 2:05 am, David Pollak  wrote:
> > Folks,
> >
> > I've found and squashed a bunch of memory retention issues in the Lift
> comet
> > stuff (and added the garbage collection for functions.)
> >
> > I've tested the fixes against the livehttp://demo.liftweb.netand there
> has
> > been no memory growth (except in Derby, but that's not Lift's problem)
> for
> > 24 hours.
> >
> > I've been using YouKit (http://yourkit.com/) to profile that
> application.
> > I've gotta say that YourKit is awesome, even for debugging remote code.
>  I'd
> > like to thank YourKit again for contributing licenses to the Lift
> > committers.
> >
> > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > practice, the actual heap size for the site never grew beyond about 10MB.
> >
> > Thanks,
> >
> > David
> >
> > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
> >
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[Marius]

Related with the above ... would it be ok with you to have a comet
long-polling interval configurable from somewhere (i.e LiftRules)? ...
currently it is hardcoded to 10 seconds.

On Feb 8, 10:37 am, Marius  wrote:
> Dave this is way awesome!
>
> I have some questions/suggestions if I may
>
> 1. Currently Lift purges the unseen functions that are older then 10
> minutes. I think it might help to make this time window configurable
> via LiftRules so that people may adjust it to fit their specific
> application needs.
>
> 2. AddLiftGCToBody should probably not renders anything related with
> GC if the GC nodes list is empty? ... or have the ability to disable
> the GC support which might be quite handy for mobile web applications
> used for limited browsers.
>
> 3. Lift for every page is starting the JS GC "daemon" that
> periodically sends the GC request up (every 75 seconds for success or
> 15 seconds for failure). Shouldn't we make these these times intervals
> configurable from LiftRules?
>
> Thoughts?
>
> Br's,
> Marius
>
> On Feb 8, 2:05 am, David Pollak  wrote:
>
> > Folks,
>
> > I've found and squashed a bunch of memory retention issues in the Lift comet
> > stuff (and added the garbage collection for functions.)
>
> > I've tested the fixes against the livehttp://demo.liftweb.netandthere has
> > been no memory growth (except in Derby, but that's not Lift's problem) for
> > 24 hours.
>
> > I've been using YouKit (http://yourkit.com/) to profile that application.
> > I've gotta say that YourKit is awesome, even for debugging remote code.  I'd
> > like to thank YourKit again for contributing licenses to the Lift
> > committers.
>
> > I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> > practice, the actual heap size for the site never grew beyond about 10MB.
>
> > Thanks,
>
> > David
>
> > PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
>
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: Serving text/html to IE

[Marius]

Try IE developer toolbar
http://www.microsoft.com/downloadS/details.aspx?familyid=E59C3964-672D-4511-BB3E-2D5E1DB91038&displaylang=en

But firebug is way more superior ... go figure :)

Br's,
Marius

On Feb 7, 8:54 pm, "Charles F. Munat"  wrote:
> Thanks for all the replies. I couldn't agree more: no reason not to
> serve as XHTML. But damn all this DOCTYPE/Quirks/Standards mode stuff is
> a pain! Not really much of an improvement over the last dozen years.
> Maybe someday... (XHTML5?).
>
> As it turns out, I figured out after beating my head against the wall
> for quite some time, that the issue was that I left out the //  on the script on that particular page, and thus the XML
> parser was converting " to " in my script. Weirdly, it worked in
> every browser except IE. Go figure.
>
> Hopefully, that will help some other poor soul who's beating his head
> against the wall at 2:30 AM. And it's good to know about the mime type.
>
> Is there a Firebug equivalent for IE?
>
> Thanks again,
> Chas.
>
> (Note to self: head looking somewhat asymmetrical. Next time, bang
> reverse side against wall until flat spots even out.)
>
> David Pollak wrote:
> > Charles,
>
> > The mime type for IE should still be text/html.
>
> > Thanks,
>
> > David
>
> > On Sat, Feb 7, 2009 at 12:25 AM, Charles F. Munat  > > wrote:
>
> >     Was there an easy way to serve as text/html to IE? I have a slide show
> >     on a page (using JQuery cycle) and it works beautifully on my static
> >     page. Same page served by lift and it's a disaster in IE6 and IE7. (Note
> >     to Bill Gates: I know you're reading this, Bill. Go die.)
>
> >     The only difference I can see in the source code is  and
> >      instead of  and , *and* I know the lift one
> >     is being served as application/xhtml+xml.
>
> >     I seem to remember something about this recently, but can't find it in
> >     the archive...
>
> >     Chas.
>
> > --
> > Lift, the simply functional web frameworkhttp://liftweb.net
> > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > Follow me:http://twitter.com/dpp
> > Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: 24 hours say the memory leaks are gone

[Marius]

Dave this is way awesome!

I have some questions/suggestions if I may


1. Currently Lift purges the unseen functions that are older then 10
minutes. I think it might help to make this time window configurable
via LiftRules so that people may adjust it to fit their specific
application needs.

2. AddLiftGCToBody should probably not renders anything related with
GC if the GC nodes list is empty? ... or have the ability to disable
the GC support which might be quite handy for mobile web applications
used for limited browsers.

3. Lift for every page is starting the JS GC "daemon" that
periodically sends the GC request up (every 75 seconds for success or
15 seconds for failure). Shouldn't we make these these times intervals
configurable from LiftRules?

Thoughts?

Br's,
Marius

On Feb 8, 2:05 am, David Pollak  wrote:
> Folks,
>
> I've found and squashed a bunch of memory retention issues in the Lift comet
> stuff (and added the garbage collection for functions.)
>
> I've tested the fixes against the livehttp://demo.liftweb.netand there has
> been no memory growth (except in Derby, but that's not Lift's problem) for
> 24 hours.
>
> I've been using YouKit (http://yourkit.com/) to profile that application.
> I've gotta say that YourKit is awesome, even for debugging remote code.  I'd
> like to thank YourKit again for contributing licenses to the Lift
> committers.
>
> I've dialed the heap size for demo.liftweb.net from 1GB to 192M.  In
> practice, the actual heap size for the site never grew beyond about 10MB.
>
> Thanks,
>
> David
>
> PS -- Yes, my confidence about making 1.0 on 2/26 is very high.
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---