-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> This means that at a properly designed site, GET is safe, but POST might
> order thousands of dollars worth of junk.  You don't want that happening
> by accident.

        Ahm, GET is most-decidedly UN-safe, but not for the same reasons.
POST doesn't "expose" the form data, whilst GET does, in the URI, which can
be bad, especially for those who put username, passwords, etc. in there, and
don't realize that it can be cached, stuck in proxies, and is likely logged
in several places in referer and access logs upstream.

> I agree, but can't offer much help just yet.  I have heard that IE can use
> the same XSLT, which might speed your testing.

        Since when can IE do XSLT? That must be a new IE7 coming out..

> Is there anything that Plucker *should* handle?

        Sure, lots of things. Text, graphics, HTML, maybe image maps?

        Javascript? No.
        Flash? No.

> From a user's perspective, we want to see the information on a web page,
> and our browser (including plucker) ought to handle any fetching for us -
> including authentication, cookies, and forms.  It doesn't quite yet, but
> it is getting closer (particularly with jpluck) and should continue to
> improve.

        Just remember that not everyone uses it for what you use it for.

> There may not be one, if the post data is essential.  (And if it weren't,
> GET would probably have worked.)

        GET is not a replacement for POST, as you know.

> Hunh?  Have you seen url-pattern doing something more than filtering which
> urls to fetch?  Transformations (including regex) are good, but I haven't
> seen it in PyPlucker yet, and I haven't seen it in JPluck without XSLT
> (which he is still debugging).

        My bad, I haven't used the Java or Python tools in quite some time,
and I'd forgotten that was there for url filtering, not internal content
filtering.


d.

perldoc -qa.j | perl -lpe '($_)=m("(.*)")'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE++gVXkRQERnB1rkoRAm8xAJ41xBhU7vpX6CsLmB5oAjAr85k9vQCghg6A
Hkv+GRATulZq2XlOvlmITU8=
=WXy2
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list

Reply via email to