Steve--

I'd be interested in this portlet code, no matter posted to the group or
emailed directly.

ttfn
--ron.  ;-)

[EMAIL PROTECTED]

___________________________________________________________________________
Make it your ambition to lead a quiet life, to mind your own business, and
to work with your
hands, just as we told you, so that your daily life may win the respect of
outsiders and so
that you will not be dependent on anybody.
1 Thessalonians 4:11-12


"sbelt" <[EMAIL PROTECTED]>@list.working-dogs.com> on 01/23/2001 08:54:43 AM

Please respond to "JetSpeed" <[EMAIL PROTECTED]>

Sent by:  <[EMAIL PROTECTED]>


To:   "JetSpeed" <[EMAIL PROTECTED]>
cc:
Subject:  Re: Feature Proposals



I actually posted to this group (~ a year ago) portlet code "HTMLFQPortlet"
that had the following characteristics:

- It extracted all markup between the <BODY> and </BODY> tags
- it modified href=, src= and action=  tags to redirect to the source
server
- it handled absolute and relative-to-current directories (ie - I did not
implement ../directory or ./directory)
- I had also implemented a parameter where you could specify which
attributes you wanted to seek to update the url's. For example, some
screens
use "url=". To minimize impact on performance, I did not want to scan the
HTML for tags too many times if I knew something about the page I was
serving up. Because my code was never commited, I assumed there was no
interest so I never shared the final version.

I am not sure why the code was never commited - perhaps commiters were too
busy, or perhaps the code was just junk (I had presumed the latter).
Anyway,
If anyone is interested, I still have a copy I could share. Should I post
it
to the group again, or does someone want it emailed directly to them? If
people use it, I would be happy to debug problems that might arise. (I have
not yet tested it with the latest version of Jetspeed)

Steve B.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Tuesday, January 23, 2001 2:29 AM
Subject: Re: Feature Proposals


>
>
>
> Ingo Rammer wrote:
>
> > Hi,
> >
> > three feature proposals. [And yes, I can do some java-developing myself
> > *hint* *hint* ;)]
> >
> > #1
> > ==========
> > Forgot Username/Password
> > ------------------------
> > When a user logs in and username/password mismatch, a link called
"Forgot
> > your password?" will be displayed. On clicking it, a new screen will be
> > shown, that allows the user to enter either Email-Address or Username.
> The
> > user's password will then be sent to the specified email-address.
>
> This is a good idea. However, it is just one way of handling forgotten
> passwords. Another way is using a reminder phrase, for example.
>
> Ideally the mechanism for handling forgotten passwords should be
pluggable.
> Perhaps it is possible to implement the handling for forgotten passwords
in
> portlets. The page to which the forgotten password link points would then
> contain the forgotten-password-handling portlet of choice.
>
> >
> > #2
> > ==========
> > Duplicate E-Mail Check
> > ----------------------
> > When a new user signs up, a check will be done against the current
> > user-database with email as the key. When a matching entry is found,
the
> > user isn't allowed to sign up again, but instead gets the possibility
to
> get
> > his password emailed to him.
>
> What would be the benefit of this behavior ?
>
> >
> > #3
> > ==========
> > WebPagePortlet
> > --------------
> > Like FileServerPortlet, but will rewrite <A HREFs, so that they point
> back
> > relative to the original website. <IMG SRCs will be rewritten, so that
> they
> > will be requested from the local cache.
> >
> > An extension to the diskcache has to be made, to allow cached entries
to
> be
> > directly requested by using http get's.
> >
> > Reason: Integration of seperately maintained (i.e. other host, other
> > country, etc.) departmental pages into a company's intranet/portal.
>
> This one is pretty hard, but surely it would be very useful. There has
been
> an extensive discussion of this topic some months ago, it might be
> worthwile
> for you to dig through the mailing-list archives. The complicated thing
> about this is that a truely generic portlet that should be able to run
any
> web application in a portlet cell would also need to refwrite JavaScript.
>
> Probably the rewriting mechanism would need to include a portlet instance
> id
> in each url.
>
> >
> > thanks for more information,
> > Ingo
>
>
> Best regards,
>
> Thomas
>
> Thomas Schaeck
> IBM Pervasive Computing Division
> Phone: +49-(0)7031-16-3479  e-mail: [EMAIL PROTECTED]
> Address: IBM Deutschland Entwicklung GmbH,
> Schoenaicher Str. 220, 71032 Boeblingen, Germany
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
> List Help?:          [EMAIL PROTECTED]



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?:          [EMAIL PROTECTED]






--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?:          [EMAIL PROTECTED]

Reply via email to