Hello all,
As Bill, I'd like to add some functions used mainly for HTTP Server/Clients that are in Caudium (and also I think in Roxen).
http_encode_string() http_encode_cookie() http_encode_url() http_decode_url()
I think that a usefull place should be in Procotols.HTTP.Utils module...
So people that need that in scripts (or even in future Roxen and Caudium) don't need to reinvent the wheel.
What do you think of that ?
/Xavier
http_encode_string() http_encode_cookie() http_encode_url() http_decode_url()
I think that a usefull place should be in Procotols.HTTP.Utils module...
What will these functions do? The names aren't that obvious.
There's a bunch of functions in the _Roxen method that should be distributed out to better locations.
Also, there's Protocol.HTTP.Server.http_decode_string and Protocol.HTTP.Server.HeaderParser ...that might do solve or more of the above problems.
(They are currently linked into the _Roxen module.)
/Mirar
The module _Roxen has the following methods
make_http_headers http_decode_string html_encode_string HeaderParser
and the module Parser has
decode_numeric_xml_entity encode_html_entities parse_html_entities
and the module Protcols.HTTP has
http_encode_query unentity http_encode_cookie http_encode_string
and the module Protocols.HTTP.Server has
http_decode_urlencoded_query
I'd say that the problem is to unify/generalize this, make sure that their implementations are fast and correct and present them for the user on a good place. I don't think that this is something that should be done now.
/ Martin Nilsson (hehe Torgny)
Previous text:
2002-12-04 17:17: Subject: Adding usufull things to Protocols.HTTP ?
Hello all,
As Bill, I'd like to add some functions used mainly for HTTP Server/Clients that are in Caudium (and also I think in Roxen).
http_encode_string() http_encode_cookie() http_encode_url() http_decode_url()
I think that a usefull place should be in Procotols.HTTP.Utils module...
So people that need that in scripts (or even in future Roxen and Caudium) don't need to reinvent the wheel.
What do you think of that ?
/Xavier
/ Xavier Beaudouin - Kiwi
Le mercredi, 4 déc 2002, à 21:40 Europe/Paris, Martin Nilsson (hehe Torgny) @ Pike (-) developers forum a écrit :
The module _Roxen has the following methods
make_http_headers http_decode_string html_encode_string HeaderParser
and the module Parser has
decode_numeric_xml_entity encode_html_entities parse_html_entities
and the module Protcols.HTTP has
http_encode_query unentity http_encode_cookie http_encode_string
and the module Protocols.HTTP.Server has
http_decode_urlencoded_query
I'd say that the problem is to unify/generalize this, make sure that their implementations are fast and correct and present them for the user on a good place. I don't think that this is something that should be done now.
Humm... Also maybe document that as well... I can't figure why _Roxen module is not on autodocs.. (Did I miss something inside the source ?).
/Xavier
Humm... Also maybe document that as well... I can't figure why _Roxen module is not on autodocs.. (Did I miss something inside the source ?).
Actually, I can't figure out why _Roxen is at all...
/ David Hedbor
Previous text:
2002-12-05 10:23: Subject: Re: Adding usufull things to Protocols.HTTP ?
Le mercredi, 4 déc 2002, à 21:40 Europe/Paris, Martin Nilsson (hehe Torgny) @ Pike (-) developers forum a écrit :
The module _Roxen has the following methods
make_http_headers http_decode_string html_encode_string HeaderParser
and the module Parser has
decode_numeric_xml_entity encode_html_entities parse_html_entities
and the module Protcols.HTTP has
http_encode_query unentity http_encode_cookie http_encode_string
and the module Protocols.HTTP.Server has
http_decode_urlencoded_query
I'd say that the problem is to unify/generalize this, make sure that their implementations are fast and correct and present them for the user on a good place. I don't think that this is something that should be done now.
Humm... Also maybe document that as well... I can't figure why _Roxen module is not on autodocs.. (Did I miss something inside the source ?).
/Xavier
/ Brevbäraren
pike-devel@lists.lysator.liu.se