Re: Cross-Context Session Replication

2005-12-03 Thread Peter Rossbach

Yes,

I implement this idea inside the ReplicationValve or a new one. I thing 
we support cross context session replication  inside 5.5.14.

Thanx
Peter

Remy Maucherat schrieb:


Peter Rossbach wrote:


Hey,

I am highly interessed to support cross-context for cluster session 
replication. The session.endAccess is a neat place

for support this. Please, let us discuss how we can use it.



In your ClusteredSession, you can override endAccess (don't forget to 
call the superclass) and populate a thread local structure of some 
sort, or something like that. Then the valve looks at the structure 
and replicates all the sessions that need to be replicated.


Rémy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 35710] - Cross-Context Session Replication

2005-12-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35710.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35710


[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|tomcat- |[EMAIL PROTECTED]
   |[EMAIL PROTECTED]  |
Summary|Enable Session Replication  |Cross-Context Session
   |via Cross Context calls |Replication




--- Additional Comments From [EMAIL PROTECTED]  2005-12-04 06:16 ---
Further discussion of the issue can be found here:
http://www.mail-archive.com/dev%40tomcat.apache.org/msg01312.html

Peter Rossbach now plans to implement Cross-Context Session Replication in
release 5.5.14.  The proposed solution discussed by Remy and Peter is to use the
endAccess method in ClusteredSession to populate a thread-local that will
contain the list of all the sessions that were modified and that need to be
replicated.  Then the ReplicationValve can use this thread-local to perform the
replication of all the affected sessions.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cross-Context Session Replication

2005-12-03 Thread John Lewis

Peter,

This is excellent news!  We are very excited that you are going to be 
working on this.


There was already any entry in ASF Bugzilla for this issue: bug #35710. 
 I have taken the liberty of updating the notes to reflect this 
discussion and of assigning it to you -- I hope that is alright.


Please let us know if there is anything we can do to support you in 
this.  Thanks so much!


John


Peter Rossbach wrote:

Yes,

I implement this idea inside the ReplicationValve or a new one. I thing 
we support cross context session replication  inside 5.5.14.

Thanx
Peter

Remy Maucherat schrieb:


Peter Rossbach wrote:


Hey,

I am highly interessed to support cross-context for cluster session 
replication. The session.endAccess is a neat place

for support this. Please, let us discuss how we can use it.




In your ClusteredSession, you can override endAccess (don't forget to 
call the superclass) and populate a thread local structure of some 
sort, or something like that. Then the valve looks at the structure 
and replicates all the sessions that need to be replicated.


Rémy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cross-Context Session Replication

2005-12-01 Thread Remy Maucherat

John Lewis wrote:
As was discussed here over the summer, there is a need in the JSR-168 
Portlet community to use cross-context access so that a portal webapp 
can communicate with various portlet webapps.  Unfortunately, session 
replication in a Tomcat cluster does not occur when one webapp accesses 
another webapp's context and changes occur in the session of the target 
webapp.


Unicon now has several clients that are extremely eager to see 
cross-context session replication support built into Tomcat.  Given that 
this work would be difficult for someone not already familiar with the 
Tomcat code, are there any experienced Tomcat developers out there who 
would be interested in doing this work for pay?  Of course we are eager 
to have this change incorporated into the main Tomcat code, so having an 
existing Tomcat committer do this would be ideal.


If anyone qualified is interested, please contact me directly.  We will 
undertake the effort ourselves if necessary, but obviously we would 
prefer to find a community-oriented solution to the problem.


I proposed to use the session.endAccess method to do that, but nobody 
seemed interested in actually implementing it.


Rémy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cross-Context Session Replication

2005-12-01 Thread Peter Rossbach

Hey,

I am highly interessed to support cross-context for cluster session 
replication. The session.endAccess is a neat place

for support this. Please, let us discuss how we can use it.

Any idea
Peter

Remy Maucherat schrieb:


John Lewis wrote:

As was discussed here over the summer, there is a need in the JSR-168 
Portlet community to use cross-context access so that a portal webapp 
can communicate with various portlet webapps.  Unfortunately, session 
replication in a Tomcat cluster does not occur when one webapp 
accesses another webapp's context and changes occur in the session of 
the target webapp.


Unicon now has several clients that are extremely eager to see 
cross-context session replication support built into Tomcat.  Given 
that this work would be difficult for someone not already familiar 
with the Tomcat code, are there any experienced Tomcat developers out 
there who would be interested in doing this work for pay?  Of course 
we are eager to have this change incorporated into the main Tomcat 
code, so having an existing Tomcat committer do this would be ideal.


If anyone qualified is interested, please contact me directly.  We 
will undertake the effort ourselves if necessary, but obviously we 
would prefer to find a community-oriented solution to the problem.



I proposed to use the session.endAccess method to do that, but nobody 
seemed interested in actually implementing it.


Rémy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]