You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Gary Lawrence Murphy <ga...@canada.com> on 2002/12/30 21:21:01 UTC
Velocity Java Applet portlet?
Is there a standard portlet suited for maintaining a session state in
an applet across page-views? What I need to do is to launch a jabber
applet, and pre-set the parameters with the login/pw of the current
$user
Since this requires security constraints, it seems best suited as a
cached portlet, but if the person shifts to another screen and then
returns, the applet will have lost its state; I'd want it to maintain
the current user state until the session times out.
Is this possible? Would the normal Velocity portlet do the trick?
--
Gary Lawrence Murphy - garym@teledyn.com - TeleDynamics Communications
- blog: http://www.teledyn.com/mt/ - biz: http://teledyn.com/ -
"Computers are useless. They can only give you answers." (Picasso)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity Java Applet portlet?
Posted by Gary Lawrence Murphy <ga...@canada.com>.
>>>>> "D" == David Sean Taylor <da...@bluesunrise.com> writes:
D> On Monday, December 30, 2002, at 12:21 PM, Gary Lawrence Murphy
D> wrote:
>> Is there a standard portlet suited for maintaining a session
>> state in an applet across page-views? What I need to do is to
>> launch a jabber applet, and pre-set the parameters with the
>> login/pw of the current $user
D> The user state for the current session is always there for you
D> and accessible from any portlet. To get the current user:
D> rundata.getUser()
This is not quite what I need: A Java applet (or an activeX control)
will reset if the page loses focus, so what I really wondered was
if the caching would help, and the more I thought about it, the
more it seemed unfeasible because caching is done on the browser side.
The good news is that I was asking the wrong question: Instead of
coding a jabber client as an applet, many of the functions could be
coded as a per-session tool service that feed a Velocity portlet. I'd
be left with the problem of new-message and other state-change
notifications, but these could go into the static left margin and the
bulk of the messaging interface could then use the portlet framework.
For now, though, I just launch a floating window with the applet in
it -- it's ugly, but it lets me get on with other work ;)
--
Gary Lawrence Murphy - garym@teledyn.com - TeleDynamics Communications
- blog: http://www.teledyn.com/mt/ - biz: http://teledyn.com/ -
"Computers are useless. They can only give you answers." (Picasso)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity Java Applet portlet?
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Monday, December 30, 2002, at 12:21 PM, Gary Lawrence Murphy wrote:
>
> Is there a standard portlet suited for maintaining a session state in
> an applet across page-views? What I need to do is to launch a jabber
> applet, and pre-set the parameters with the login/pw of the current
> $user
>
> Since this requires security constraints, it seems best suited as a
> cached portlet, but if the person shifts to another screen and then
> returns, the applet will have lost its state; I'd want it to maintain
> the current user state until the session times out.
>
> Is this possible? Would the normal Velocity portlet do the trick?
>
The user state for the current session is always there for you and
accessible from any portlet. To get the current user: rundata.getUser()
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>