Re: Maintain server state of a page + Javascript page navigation
Yes, Ajax framework uses prototype. You can use jquery in your own code, but you have to use the jquery prototype compatibility library. As far as why we use prototype -- it was the most popular library when we started Ajax.framework, and was the primary framework used by rails as well. The effort and cost to everyone to change that decision now would be substantial. ms On Jul 9, 2009, at 2:35 AM, shravan kumar wrote: Hi Mike, Yes Mike, I get one WO page as response and that is split into many sub-pages for user data manageability. I will check out AjaxPing component. I was just wondering why do we use prototype.js in our Ajax framework or most of Wonder projects (pardon me, if am wrong, but that was my understanding sometime ago). I wish if we have jQuery as our javascript framework and I use jQuery in most of my projects!!! Thank You, Shravan Kumar. M -- Thursday, July 9, 2009 1:50 AM From: "Mike Schrag" To: "WO Dev Group" if you're keeping them on a single page for your entire process and rendering the wizard process in js, then you won't be transitioning across pages, so you won't be burning your cache. at that point, all that matters is that your session is kept alive. AjaxBusyIndicator doesn't ping -- it just shows a spinner when an ajax function is occurring ... AjaxPing (iirc) is the component you want? I'm not in that workspace right now, so I don't have it handy ... ms On Jul 8, 2009, at 3:37 PM, shravan kumar wrote: Hi Mike, Thanks for your response Mike. I hope you are referring to "AjaxBusyIndicator" in the Wonder/Ajax Examples for ping in the background. As you say, "Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons.", do we have any good solution to get away from this issue and keep all my elements/ actions in my component up-to-date? Thank You, Shravan Kumar. M Wednesday, July 8, 2009 7:02 PM From: "Mike Schrag" To: "WO Dev Group" Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons. Not sure what you mean about using component actions and direct actions freely. Component actions are powerful but just have intrinsic limitations. If you have a long running process on the client side that could reasonably run longer than your session timeout, you either have to keep the session alive with some sort of ping in the background (I think Ajax framework has a component for this), or you need to switch to direct actions. DA's can fully access the session, but you have the same issue -- if your client process takes longer than your session lifetime, you're going to lose that information. In the DA case, that either means the same sort of ping process, or it means making your app stateless (i.e. client side tracks and passes in the current state). ms On Jul 8, 2009, at 2:01 AM, shravan kumar wrote: Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged- in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/ Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, sh
Re: Maintain server state of a page + Javascript page navigation
Hi Mike, Yes Mike, I get one WO page as response and that is split into many sub-pages for user data manageability. I will check out AjaxPing component. I was just wondering why do we use prototype.js in our Ajax framework or most of Wonder projects (pardon me, if am wrong, but that was my understanding sometime ago). I wish if we have jQuery as our javascript framework and I use jQuery in most of my projects!!! Thank You, Shravan Kumar. M -- Thursday, July 9, 2009 1:50 AM From: "Mike Schrag" To: "WO Dev Group" if you're keeping them on a single page for your entire process and rendering the wizard process in js, then you won't be transitioning across pages, so you won't be burning your cache. at that point, all that matters is that your session is kept alive. AjaxBusyIndicator doesn't ping -- it just shows a spinner when an ajax function is occurring ... AjaxPing (iirc) is the component you want? I'm not in that workspace right now, so I don't have it handy ... ms On Jul 8, 2009, at 3:37 PM, shravan kumar wrote: Hi Mike, Thanks for your response Mike. I hope you are referring to "AjaxBusyIndicator" in the Wonder/Ajax Examples for ping in the background. As you say, "Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons.", do we have any good solution to get away from this issue and keep all my elements/ actions in my component up-to-date? Thank You, Shravan Kumar. M Wednesday, July 8, 2009 7:02 PM From: "Mike Schrag" To: "WO Dev Group" Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons. Not sure what you mean about using component actions and direct actions freely. Component actions are powerful but just have intrinsic limitations. If you have a long running process on the client side that could reasonably run longer than your session timeout, you either have to keep the session alive with some sort of ping in the background (I think Ajax framework has a component for this), or you need to switch to direct actions. DA's can fully access the session, but you have the same issue -- if your client process takes longer than your session lifetime, you're going to lose that information. In the DA case, that either means the same sort of ping process, or it means making your app stateless (i.e. client side tracks and passes in the current state). ms On Jul 8, 2009, at 2:01 AM, shravan kumar wrote: Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged-in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: > Hi Group, > > Could you please advise me a solution to achieve below functionality: > > Scenario: > - > > I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. > > Once this data from the server has arrived, we will be
Re: Maintain server state of a page + Javascript page navigation
if you're keeping them on a single page for your entire process and rendering the wizard process in js, then you won't be transitioning across pages, so you won't be burning your cache. at that point, all that matters is that your session is kept alive. AjaxBusyIndicator doesn't ping -- it just shows a spinner when an ajax function is occurring ... AjaxPing (iirc) is the component you want? I'm not in that workspace right now, so I don't have it handy ... ms On Jul 8, 2009, at 3:37 PM, shravan kumar wrote: Hi Mike, Thanks for your response Mike. I hope you are referring to "AjaxBusyIndicator" in the Wonder/Ajax Examples for ping in the background. As you say, "Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons.", do we have any good solution to get away from this issue and keep all my elements/ actions in my component up-to-date? Thank You, Shravan Kumar. M Wednesday, July 8, 2009 7:02 PM From: "Mike Schrag" To: "WO Dev Group" Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons. Not sure what you mean about using component actions and direct actions freely. Component actions are powerful but just have intrinsic limitations. If you have a long running process on the client side that could reasonably run longer than your session timeout, you either have to keep the session alive with some sort of ping in the background (I think Ajax framework has a component for this), or you need to switch to direct actions. DA's can fully access the session, but you have the same issue -- if your client process takes longer than your session lifetime, you're going to lose that information. In the DA case, that either means the same sort of ping process, or it means making your app stateless (i.e. client side tracks and passes in the current state). ms On Jul 8, 2009, at 2:01 AM, shravan kumar wrote: Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged- in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/ Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: > Hi Group, > > Could you please advise me a solution to achieve below functionality: > > Scenario: > - > > I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. > > Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. > > There can be around 40 sub-pages or more. > > While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub- page (like we see in ajax implementations) and just update a particular field. > > I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by t
Re: Maintain server state of a page + Javascript page navigation
Hi Mike, Thanks for your response Mike. I hope you are referring to "AjaxBusyIndicator" in the Wonder/Ajax Examples for ping in the background. As you say, "Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons.", do we have any good solution to get away from this issue and keep all my elements/ actions in my component up-to-date? Thank You, Shravan Kumar. M Wednesday, July 8, 2009 7:02 PM From: "Mike Schrag" To: "WO Dev Group" Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons. Not sure what you mean about using component actions and direct actions freely. Component actions are powerful but just have intrinsic limitations. If you have a long running process on the client side that could reasonably run longer than your session timeout, you either have to keep the session alive with some sort of ping in the background (I think Ajax framework has a component for this), or you need to switch to direct actions. DA's can fully access the session, but you have the same issue -- if your client process takes longer than your session lifetime, you're going to lose that information. In the DA case, that either means the same sort of ping process, or it means making your app stateless (i.e. client side tracks and passes in the current state). ms On Jul 8, 2009, at 2:01 AM, shravan kumar wrote: Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged-in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: > Hi Group, > > Could you please advise me a solution to achieve below functionality: > > Scenario: > - > > I have a page which gets all the data like text content [3000 lines or more], > images info [about 500 or more] once when the user requests for this page. > > Once this data from the server has arrived, we will be displaying this whole > data part by part by splitting this data into sub-pages through javascript. > So, user actually sees the sub-page rather the whole page received from the > server. > > There can be around 40 sub-pages or more. > > While navigating through each of these sub-pages user may perform a server > action like edit some text and save, rotate an image and save, ... and all > these actions do not refresh the whole page/ sub-page (like we see in ajax > implementations) and just update a particular field. > > I assume that there might be some time-gap say 10 minutes or more between > each of the server actions performed by the user. > > During these times as you know, we have to maintain the session of this user > in the server (this can be achieved through lets say session timeout value), > state of this page in the server, ... > > Problem: > - > How can I maintain the state of this page (generally whenever we do a submit > WO app returns with a new context info, correct?), so all my actions are > valid and there are issues of Broken pipe/ page not in the cache/ ... > > I thought of just pinging the server every few seconds for some dummy data > like: how are you doing? or some
Re: Maintain server state of a page + Javascript page navigation
Yes, if you bind to an action that falls out of the backtrack cache, you'll get that error. This can happen for several reasons. Not sure what you mean about using component actions and direct actions freely. Component actions are powerful but just have intrinsic limitations. If you have a long running process on the client side that could reasonably run longer than your session timeout, you either have to keep the session alive with some sort of ping in the background (I think Ajax framework has a component for this), or you need to switch to direct actions. DA's can fully access the session, but you have the same issue -- if your client process takes longer than your session lifetime, you're going to lose that information. In the DA case, that either means the same sort of ping process, or it means making your app stateless (i.e. client side tracks and passes in the current state). ms On Jul 8, 2009, at 2:01 AM, shravan kumar wrote: Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged- in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/ Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: Hi Group, Could you please advise me a solution to achieve below functionality: Scenario: - I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. There can be around 40 sub-pages or more. While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub- page (like we see in ajax implementations) and just update a particular field. I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by the user. During these times as you know, we have to maintain the session of this user in the server (this can be achieved through lets say session timeout value), state of this page in the server, ... Problem: - How can I maintain the state of this page (generally whenever we do a submit WO app returns with a new context info, correct?), so all my actions are valid and there are issues of Broken pipe/ page not in the cache/ ... I thought of just pinging the server every few seconds for some dummy data like: how are you doing? or something like gmail does? However, I do not know how to exactly implement this behavior. Please advise. Thanks in advance, Shravan Kumar. M ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com This email sent to msch...@mdimension.com __ Do You Yaho
Re: Maintain server state of a page + Javascript page navigation
Thanks for your response Mike. What is Giandiua btw? Google says it is a Chocolate from Italy!!! The page am referring is just one of the pages of a wizard, which has sub-pages. The whole wizard runs through component actions. I was actually about following situation: When we have long response component displayed upon initiating a request, and we see long response until we have a response. Once after the response let's say I just hide long response component and show the main component, now user cannot perform any actions in this main component and we might receive errors like: You have exceeded 30 pages limit/ page out of cache... this is because the context bound to the action element is older. Am I correct (Mike) ? I understand by your saying switching to direct actions, we can get away from this issue if we use direct actions. But am wondering if I can use component actions and direct actions freely. I hope I can validate whether the direct action request is initiated by a logged-in valid user, so my direct actions are not floating freely. --- If I use component actions, can you advise me how can I have all the elements, app in the latest context? Thank You, Shravan Kumar. M -- Monday, July 6, 2009 7:14 PM From: "Mike Schrag" To: "WO Dev Group" seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: Hi Group, Could you please advise me a solution to achieve below functionality: Scenario: - I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. There can be around 40 sub-pages or more. While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub-page (like we see in ajax implementations) and just update a particular field. I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by the user. During these times as you know, we have to maintain the session of this user in the server (this can be achieved through lets say session timeout value), state of this page in the server, ... Problem: - How can I maintain the state of this page (generally whenever we do a submit WO app returns with a new context info, correct?), so all my actions are valid and there are issues of Broken pipe/ page not in the cache/ ... I thought of just pinging the server every few seconds for some dummy data like: how are you doing? or something like gmail does? However, I do not know how to exactly implement this behavior. Please advise. Thanks in advance, Shravan Kumar. M ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com This email sent to msch...@mdimension.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Maintain server state of a page + Javascript page navigation
Hi David, Thanks for your insight. I may be late to drop this Q in the WO Group. I have designed most of the app and is working fine. Basically this module is just one part of the my application. I have no idea of JavaClient. Should it be installed in the individual users machines? Can I move my current code to this app? What all changes you anticipate? How can I sysnc it with my regular web app? Please advise. Thank You, Shravan Kumar. M --- On Mon, 7/6/09, David Avendasora wrote: From: David Avendasora Subject: Re: Maintain server state of a page + Javascript page navigation To: "shravan kumar" Cc: "WO Dev Group" Date: Monday, July 6, 2009, 6:24 PM On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: > Hi Group, > > Could you please advise me a solution to achieve below functionality: > > Scenario: > - > > I have a page which gets all the data like text content [3000 lines or more], > images info [about 500 or more] once when the user requests for this page. > > Once this data from the server has arrived, we will be displaying this whole > data part by part by splitting this data into sub-pages through javascript. > So, user actually sees the sub-page rather the whole page received from the > server. > > There can be around 40 sub-pages or more. > > While navigating through each of these sub-pages user may perform a server > action like edit some text and save, rotate an image and save, ... and all > these actions do not refresh the whole page/ sub-page (like we see in ajax > implementations) and just update a particular field. > > I assume that there might be some time-gap say 10 minutes or more between > each of the server actions performed by the user. > > During these times as you know, we have to maintain the session of this user > in the server (this can be achieved through lets say session timeout value), > state of this page in the server, ... > > Problem: > - > How can I maintain the state of this page (generally whenever we do a submit > WO app returns with a new context info, correct?), so all my actions are > valid and there are issues of Broken pipe/ page not in the cache/ ... Unless I'm missing something, you can just extend the length of the Session timeout to be what you anticipate the longest a user will need to respond. 10 minutes I believe is the default, but you can make it anything. Editing Contexts (your user's pools of objects) are maintained as part of the user's Session and you control which editing context is used, or if a new one is created for each action. Maintaining state is one of WO's core functions, you just have to determine exactly what state and for how long you want to maintain it for your particular situation > I thought of just pinging the server every few seconds for some dummy data > like: how are you doing? or something like gmail does? However, I do not know > how to exactly implement this behavior. You should not need to do this at all. WO will maintain state as long as the session hasn't timed out or you don't start using a different editing context. With all this said, it sounds like you are trying to implement a rich client in a web UI. Have you considered Java Client at all for this functionality? It would make managing the client-server interaction much easier since you will actually have EOs on the client that you can manipulate using normal Java instead of having to write Javascript to do it. Dave ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Maintain server state of a page + Javascript page navigation
seems to me like you're swimming against the tide here ... i think you need to rethink this architecture. you're basically sending the users the entire site, which makes this more of a Sproutcore/Giandiua/etc workflow, and mixing component actions into this style of app is going to be very tricky. I would recommend switching to directactions. you could keep a session alive with a ping if you really need it to be sessionful, but trying to actually use WOForms in this thing is going to be an endless headache imo. On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: Hi Group, Could you please advise me a solution to achieve below functionality: Scenario: - I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. There can be around 40 sub-pages or more. While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub- page (like we see in ajax implementations) and just update a particular field. I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by the user. During these times as you know, we have to maintain the session of this user in the server (this can be achieved through lets say session timeout value), state of this page in the server, ... Problem: - How can I maintain the state of this page (generally whenever we do a submit WO app returns with a new context info, correct?), so all my actions are valid and there are issues of Broken pipe/ page not in the cache/ ... I thought of just pinging the server every few seconds for some dummy data like: how are you doing? or something like gmail does? However, I do not know how to exactly implement this behavior. Please advise. Thanks in advance, Shravan Kumar. M ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com This email sent to msch...@mdimension.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Maintain server state of a page + Javascript page navigation
On Jul 6, 2009, at 7:54 AM, shravan kumar wrote: Hi Group, Could you please advise me a solution to achieve below functionality: Scenario: - I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. There can be around 40 sub-pages or more. While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub- page (like we see in ajax implementations) and just update a particular field. I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by the user. During these times as you know, we have to maintain the session of this user in the server (this can be achieved through lets say session timeout value), state of this page in the server, ... Problem: - How can I maintain the state of this page (generally whenever we do a submit WO app returns with a new context info, correct?), so all my actions are valid and there are issues of Broken pipe/ page not in the cache/ ... Unless I'm missing something, you can just extend the length of the Session timeout to be what you anticipate the longest a user will need to respond. 10 minutes I believe is the default, but you can make it anything. Editing Contexts (your user's pools of objects) are maintained as part of the user's Session and you control which editing context is used, or if a new one is created for each action. Maintaining state is one of WO's core functions, you just have to determine exactly what state and for how long you want to maintain it for your particular situation I thought of just pinging the server every few seconds for some dummy data like: how are you doing? or something like gmail does? However, I do not know how to exactly implement this behavior. You should not need to do this at all. WO will maintain state as long as the session hasn't timed out or you don't start using a different editing context. With all this said, it sounds like you are trying to implement a rich client in a web UI. Have you considered Java Client at all for this functionality? It would make managing the client-server interaction much easier since you will actually have EOs on the client that you can manipulate using normal Java instead of having to write Javascript to do it. Dave ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Maintain server state of a page + Javascript page navigation
Hi Group, Could you please advise me a solution to achieve below functionality: Scenario: - I have a page which gets all the data like text content [3000 lines or more], images info [about 500 or more] once when the user requests for this page. Once this data from the server has arrived, we will be displaying this whole data part by part by splitting this data into sub-pages through javascript. So, user actually sees the sub-page rather the whole page received from the server. There can be around 40 sub-pages or more. While navigating through each of these sub-pages user may perform a server action like edit some text and save, rotate an image and save, ... and all these actions do not refresh the whole page/ sub-page (like we see in ajax implementations) and just update a particular field. I assume that there might be some time-gap say 10 minutes or more between each of the server actions performed by the user. During these times as you know, we have to maintain the session of this user in the server (this can be achieved through lets say session timeout value), state of this page in the server, ... Problem: - How can I maintain the state of this page (generally whenever we do a submit WO app returns with a new context info, correct?), so all my actions are valid and there are issues of Broken pipe/ page not in the cache/ ... I thought of just pinging the server every few seconds for some dummy data like: how are you doing? or something like gmail does? However, I do not know how to exactly implement this behavior. Please advise. Thanks in advance, Shravan Kumar. M ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
