- cxml-devel - mailman3.common-lisp.net

[cxml-devel] out of synch with cl-ppcre
by Ben Hyde 16 Aug '08

16 Aug '08

The code around *convert-char-class-to-hash* in nppcre.lisp fails now since cl-ppcre::convert-char-class-to-hash is no more. I was able to get things to compile by commenting it out. I haven't a clue what that's going to break ...

1 0

[cxml-devel] Problems with Xuriella on LispWorks
by Jochen Schmidt 15 Jun '08

15 Jun '08

Hi, I had problems compiling Xuriella (a current clone from the git repository) with LispWorks. There were a few problems regarding the order of the definitions. Common Lisp is quite sensitive to the order of definitions if macros or structures are used. You have to define a structure before you use it (this also entails accesses using structure-slot-accessors). You also have to define a macro before compiling a function using that macro. I've fixed those issues locally here and Xuriella runs now withing my LispWorks setup. If you're interested in what I've done; how should I make my changes available? ciao, Jochen -- Jochen Schmidt CRISPYLOGICS Julienstr. 1, 90419 Nuremberg Fon +49 (0)911 517 999 82 Fax +49 (0)911 517 999 83 mailto:info@crispylogics.com http://www.crispylogics.com

2 1

[cxml-devel] [PATCH] Make pathname-to-uri handle :back/:up components in directory.
by Pierre R. Mai 07 Jun '08

07 Jun '08

Previously cxml:parse-file would cause an error in pathname-to-uri when handed a pathname with :back or :up entries in the directory component. This change ensures that a suitable base-uri is generated in those cases. --- xml/xml-parse.lisp | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/xml/xml-parse.lisp b/xml/xml-parse.lisp index eb8e338..546b60b 100644 --- a/xml/xml-parse.lisp +++ b/xml/xml-parse.lisp @@ -3030,7 +3030,9 @@ #-cxml-system::uri-is-namestring (defun pathname-to-uri (pathname) (let ((path - (append (pathname-directory pathname) + (append (mapcar #'(lambda (x) (cond ((member x '(:up :back)) "..") + (t x))) + (pathname-directory pathname)) (list (if (specific-or (pathname-type pathname)) (concatenate 'string -- 1.5.6.rc1.15.g03aab

2 1

[cxml-devel] charset-windows.patch
by Pierre R. Mai 07 Jun '08

07 Jun '08

Hello everyone, having had the unfortunate opportunity to need to parse XML files with Windows encodings, I've added created the following patch against current CVS, which adds encodings for Windows-1250,1251,1252,1253,1254,1255 and 1257 (1256 and 1258 not being in wide usage hereabouts). The patch also adds ISO-8859-13 (very similar to 1257) and the remaining official aliases from IANA for the ISO-8859-14 and ISO-8859-15 encodings for completeness. Regs, Pierre. -- Pierre R. Mai <pmai(a)pmsf.de> PMSF IT Consulting Pierre R. Mai http://www.pmsf.de/ Ludwig-Thoma-Str. 11 Schleißheimer Str. 263 87724 Ottobeuren 80809 München Tel. +49(0)8332/93669-13 +49(0)89/35061750 Fax +49(0)8332/93669-03 Germany

2 1

[cxml-devel] charset-windows.patch
by Pierre R. Mai 03 Jun '08

03 Jun '08

[ Sorry for the duplication, but it seems I accidentally signed the previous mail, which can cause problems with patch and mailman ] Hello everyone, having had the unfortunate opportunity to need to parse XML files with Windows encodings, I've added created the following patch against current CVS, which adds encodings for Windows-1250,1251,1252,1253,1254,1255 and 1257 (1256 and 1258 not being in wide usage hereabouts). The patch also adds ISO-8859-13 (very similar to 1257) and the remaining official aliases from IANA for the ISO-8859-14 and ISO-8859-15 encodings for completeness. Regs, Pierre. -- Pierre R. Mai <pmai(a)pmsf.de> PMSF IT Consulting Pierre R. Mai http://www.pmsf.de/ Ludwig-Thoma-Str. 11 Schleißheimer Str. 263 87724 Ottobeuren 80809 München Tel. +49(0)8332/93669-13 +49(0)89/35061750 Fax +49(0)8332/93669-03 Germany

1 0

[cxml-devel] Problem compiling current git version
by Ralf Mattes 20 May '08

20 May '08

Hello list, this error occurs after a fresh git-clone: -+ Errors (1) `-- SB-INT:SIMPLE-READER-PACKAGE-ERROR at 5492 (line 123, column 30) on #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/unparse.lisp" {C538FC9}>: Symbol "FIND-OUTPUT-ENCODING" not found in the RUNES package. This is with sbcl-1.0.15 / Ubuntu w. CLC and (CVS) slime. Cheers, RalfD

2 3

[cxml-devel] cxml dependency in closure-html
by Nathan Bird 20 May '08

20 May '08

closure-html/src/parse/unparse.lisp line 33 has a reference to cxml::find-output-encoding. The closure-html.asd doesn't specify cxml as a dependency. From what I understand of the desired layout we don't want it to, so maybe that function should move up to closure common? Hope that helps, Nathan

2 1

[cxml-devel] Error in ystream.lisp while loading closure-common
by Chaitanya Gupta 17 May '08

17 May '08

Hi, I just installed the latest git snapshot of closure-common. I ran into the following error while loading it - -- x -- (LAMBDA (RUNES:ROD RUNES::INDEX) (BLOCK RUNES:RUNE (CHAR RUNES:ROD RUNES::INDEX))) is not a valid function spec [Condition of type TYPE-ERROR] Restarts: 0: [NIL] retry the compilation of /Users/chaitanya/lisp/libs/site/closure-common/ystream.lisp 1: [NIL] continue compiling /Users/chaitanya/lisp/libs/site/closure-common/ystream.lisp but generate no output file 2: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL @ #x113a195a> on #<CLOSURE-COMMON-SYSTEM::CLOSURE-SOURCE-FILE "ystream" @ #x103f0822>. 3: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL @ #x113a195a> on #<CLOSURE-COMMON-SYSTEM::CLOSURE-SOURCE-FILE "ystream" @ #x103f0822> as having been successful. 4: [ABORT-REQUEST] Abort handling SLIME request. 5: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<TYPE-ERROR @ #x114e80b2>) 1: (SWANK:SWANK-DEBUGGER-HOOK #<TYPE-ERROR @ #x114e80b2> #<Function SWANK-DEBUGGER-HOOK>) 2: (ERROR TYPE-ERROR :DATUM #1=(LAMBDA (RUNES:ROD RUNES::INDEX) (BLOCK RUNES:RUNE (CHAR RUNES:ROD RUNES::INDEX))) :EXPECTED-TYPE EXCL::FUNCTION-NAME :FORMAT-CONTROL "~s is not a valid function spec" :FORMAT-ARGUMENTS (#1#)) 3: (FBOUNDP (LAMBDA (RUNES:ROD RUNES::INDEX) (BLOCK RUNES:RUNE (CHAR RUNES:ROD RUNES::INDEX)))) 4: (SYSTEM:FUNCTION-INFORMATION (LAMBDA (RUNES:ROD RUNES::INDEX) (BLOCK RUNES:RUNE (CHAR RUNES:ROD RUNES::INDEX))) #<Augmentable COMPILER environment 1 1 1 1 1 15>) 5: (GET-SETF-EXPANSION ((LAMBDA (RUNES:ROD RUNES::INDEX) (BLOCK RUNES:RUNE #)) RUNES::TMP 0) #<Augmentable COMPILER environment 1 1 1 1 1 15>) 6: (SETF (SETF (RUNES:RUNE RUNES::TMP 0) RUNES:RUNE) #<Augmentable COMPILER environment 1 1 1 1 1 15>) 7: (FUNCALL #<Function SETF @ #x100dce22> (SETF (RUNES:RUNE RUNES::TMP 0) RUNES:RUNE) #<Augmentable COMPILER environment 1 1 1 1 1 15>) 8: (COMPILER::PA-COMPILE (SETF (RUNES:RUNE RUNES::TMP 0) RUNES:RUNE) NIL) -- x -- The error occurred while Lisp was compiling YSTREAM-WRITE-ESCAPABLE-RUNE in ystream.lisp. To me the problem seems that RUNE is defined as a compiler-macro and its also being used as a SETF form. I am not sure whether its a problem with my Lisp or closure-common. I am using ACL 8.0 on Intel Mac OS X. It loads fine on SBCL, but DEFINLINE doesn't define any compiler macros in SBCL. Maybe that's why it loads fine here and breaks on ACL? Chaitanya

2 2

[cxml-devel] Cxml-rng and allegro issue
by Prashanth 15 May '08

15 May '08

Hi David Lichteblau, I am using cxml-rng in allegro 8.0 and I am unable to load the package, can you help me in fixing the issue? when i try to load this is the error message i get "`NIL' is not of the expected type `CHARACTER'". -- regards, Prashanth http://munichlinux.blogspot.com

2 1

[cxml-devel] ystream-unicode-p errors when serializing to character-stream
by Nathan Bird 10 May '08

10 May '08

With git head I get an error with the following: (with-output-to-string (stream) (let ((doc (dom:create-document 'rune-dom:implementation nil nil (dom:create-document-type 'rune-dom:implementation "html" "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd")))) (dom:map-document (chtml:make-character-stream-sink stream) doc :include-xmlns-attributes nil :include-doctype :full-internal-subset ))) The error as far as I've been able to track it down, is that the ystream created has a encoding slot, that is never filled. Then #'runes::ystream-unicode-p chokes when trying to inspect the encoding. We solved the error by testing the target stream when the encoding slot is null: (defun ystream-unicode-p (ystream) (let ((enc (ystream-encoding ystream))) (if enc (or (eq enc :utf-8) (eq (babel-encodings:enc-name enc) :utf-16)) #+rune-is-character (eq 'character (stream-element-type (ystream-target-stream ystream)))))) But I'm not sure that it is sound, and that function looks kind of strange anyways: what if encoding was the symbol :utf-16 or a babel-encoding object with the name :utf-8? It looks like the shift to babel-encodings is still somewhat a work-in-progress, does this help? We found this today when we switched from asdf-installed version to git HEAD because there was a problem with & getting escaped that looks like it is already fixed in git.

2 1

[cxml-devel] cxml moved to git
by David Lichteblau 13 Apr '08

13 Apr '08

Hi, in preparation for the next cxml release, both cxml itself and closure-common have been moved from CVS to git. (Until that release is done, CVS will still be available, but new development happens in git.) Mirror URLs: git clone git://repo.or.cz/cxml.git git clone git://repo.or.cz/cxml-common.git Gitweb: http://repo.or.cz/w/cxml.git http://repo.or.cz/w/closure-common.git d.

2 1

[cxml-devel] flexml: a new document model i'm playing with
by Attila Lendvai 01 Mar '08

01 Mar '08

hi! i've playing with an document builder that may be interesting for the list. the basic idea is to parse the xml into CLOS objects with their own class, so that method dispatch can be used to process the document. i need this for verrazano, to process the gccxml output. the first part of the file contains the generic flexml document builder and at the end there's some specialized code for gccxml. how it works: you can give it a default lisp package and also register namespace-uri->lisp-package mappings. when a node is encountered then a symbol is looked up in the appropriate package and make-instance is used to make the node. there's also a slot-missing specialization on it, so that it can store random slots (attributes) in a hashtable. features currently: - can resolve crossreferences, see cross-referenced-node slot type and friends - handles some slot types specially: cross-referenced-node, cross-referenced-nodes, integer, boolean, etc - can store attributes in a mixed slot/hashtable mode where simple attributes can go into the hashtable and special ones can be full-featured slots the code for now is only a proof of concept, but i wonder if there would be a place for it somewhere in a repo around cxml? it won't be bigger then a few pages so i think the most practical distribution would be to have its own .asd/package in the cxml repo/directory. but i don't want to run ahead... it even could be that i'm doing duplicate work with this. opinions? -- attila

3 6

Re: [cxml-devel] Parsing from a stream
by David Lichteblau 19 Feb '08

19 Feb '08

Quoting Chaitanya Gupta (mail(a)chaitanyagupta.com): > CL-USER> (flexi-streams:with-input-from-sequence (s *x) > (cxml:parse s (cxml-dom:make-dom-builder))) [...] > Only file streams are supported? Thanks for the report. That was a bug in PARSE, which should be fixed in cxml CVS now. (You could also use the older function CXML:PARSE-STREAM instead of the new interface CXML:PARSE. The former doesn't have the bug.) > No. The reason I am asking is because I get a (huge) XML over a socket; I > think parsing directly from the socket stream should be much more efficient > than first reading the XML into a string, and then parsing the string (is > this assumption correct?). Sure, parsing from a socket directly is the natural solution, and needs only constant space rather than O(n) space with the length of the input. (Not taking into account that the DOM tree obviously needs O(n) space.) For now, you'd have to open the socket using :element-type '(unsigned-byte 8), or take advantage of bivalent streams on Lisps that provide them. In the long term, I'll try to add support for character streams. (But note that cxml will detect the encoding declared in the XML declaration when parsing from binary streams. It won't be able to do that when the Lisp is already handling the external-format conversion in the stream. That's the primary reason binary streams are better for XML parsing.) d.

2 1

[Fwd: Re: [cxml-devel] Parsing from a stream]
by Chaitanya Gupta 19 Feb '08

19 Feb '08

Sorry, forgot to reply to the list...

1 0

[cxml-devel] Parsing from a stream
by Chaitanya Gupta 19 Feb '08

19 Feb '08

Hi, I am tring to parse an XML from a stream using CXML:PARSE. I get an error when I try that. Here's the input form and the backtrace. --- CL-USER> (with-input-from-string (s "<foo>bar</foo>") (cxml:parse s (cxml-dom:make-dom-builder))) ; Evaluation aborted can't read-byte from a string stream: #<STRING-INPUT-SIMPLE-STREAM "<foo>bar</foo>" pos 0 @ #x1108e69a> [Condition of type TYPE-ERROR] Restarts: 0: [ABORT-REQUEST] Abort handling SLIME request. 1: [ABORT] Abort entirely from this (lisp) process. Backtrace: 0: (SWANK::DEBUG-IN-EMACS #<TYPE-ERROR @ #x110fb1f2>) 1: (SWANK:SWANK-DEBUGGER-HOOK #<TYPE-ERROR @ #x110fb1f2> #<Function SWANK-DEBUGGER-HOOK>) 2: (ERROR TYPE-ERROR :DATUM #1=#<STRING-INPUT-SIMPLE-STREAM "<foo>bar</foo>" pos 0 @ #x1108e69a> :EXPECTED-TYPE STREAM :FORMAT-CONTROL "can't read-byte from a string stream: ~s" :FORMAT-ARGUMENTS (#1#)) 3: ((METHOD RUNES::FIGURE-ENCODING (STREAM)) #<STRING-INPUT-SIMPLE-STREAM "<foo>bar</foo>" pos 0 @ #x1108e69a>) 4: (RUNES:MAKE-XSTREAM #<STRING-INPUT-SIMPLE-STREAM "<foo>bar</foo>" pos 0 @ #x1108e69a> :SPEED 8192) 5: (CXML:PARSE #<STRING-INPUT-SIMPLE-STREAM "<foo>bar</foo>" pos 0 @ #x1108e69a> #<RUNE-DOM::DOM-BUILDER @ #x110fb1b2>) --- I tried this on ACL 8.0 and CXML is from CVS. Shouldn't string streams be parseable? Chaitanya

2 1

[cxml-devel] Where is the HAX package?
by Ralf Mattes 14 Dec '07

14 Dec '07

Hello list, I'm trying to use the latest CVS version of cxml but get the following error message (sbcl 1.0.10/Ubuntu): ; compiling file "/usr/share/common-lisp/source/cxml/xml/sax-handler.lisp" (written 18 NOV 2007 07:43:11 PM): ; compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 7480 (line 223, column 45) on #<SB-SYS:FD-STREAM for "file /usr/share/common-lisp/source/cxml/xml/sax-handler.lisp" {B47A331}>: ; package "HAX" not found Grepping for defpackage doesn't help: ralf@mhflaptop01:/LISP/cxml$ find -name '*lisp' | xargs grep -i defpackage ./contrib/xhtmlgen.lisp:(defpackage :xhtml-generator ./dom/dom-impl.lisp:(defpackage :rune-dom ./dom/dom-impl.lisp:(defpackage :utf8-dom ./dom/package.lisp:(defpackage :dom ./klacks/package.lisp:(defpackage klacks ./test/domtest.lisp:(defpackage :domtest ./test/domtest.lisp:(defpackage :domtest-tests ./test/xmlconf.lisp:(defpackage xmlconf ./xml/sax-tests/package.lisp:(defpackage :sax-tests ./xml/package.lisp:(defpackage :cxml ./xml/sax-handler.lisp:(defpackage :sax ./xml/xmls-compat.lisp:(defpackage cxml-xmls What _am_ i missing here? Cheers, Ralf Mattes P.S: I'm currently creating Debian/Ubuntu packages for cxml/closure-common.

2 2

[cxml-devel] New cxml releases
by David Lichteblau 21 Oct '07

21 Oct '07

Hi, a new cxml release is available. This is the first release that depends on closure-common, found in cxml CVS as a separate module and as a tarball in cxml's download directory. Users of cxml-stp and cxml-rng should also upgrade to the newest versions of these systems for compatibility with this cxml release. Other changes in this release: * Incompatible SAX changes: Added new classes sax:abstract-handler, sax:content-handler, sax:default-handler. Implementations of SAX handlers should now subclass one of these classes. * fixed make-source :buffering nil, thanks to Magnus Henoch for the report * fixed time and space usage in cases where entity references follow each other (thanks to Ivan Shvedunov for the report) * In the DOM builder, grow a buffer for string normalization exponentially, fixing a long-standing speed issue. David

1 0

[cxml-devel] Where is the closure-common system?
by Ralf Mattes 09 Oct '07

09 Oct '07

After a recent CVS update SBCL is unable to load cxml, complaining: debugger invoked on a MISSING-DEPENDENCY in thread #<THREAD "initial thread" {A806671}>: component :CLOSURE-COMMON not found, required by CXML Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-INT:SIMPLE-EVAL-IN-LEXENV (ERROR 'MISSING-DEPENDENCY :REQUIRED-BY :CXML :VERSION NIL :REQUIRES :CLOSURE-COMMON) #<NULL-LEXENV>) 0] 0 This did not happen with earlier versions. I can check out a closure-common module from CVS but that doesn't conatain a ASDF definition .... TIA Ralf Mattes

2 2

[cxml-devel] CXML::P/CONTENT causes heap exhaustion due to deep recursion where there are too many entity references
by Ivan Shvedunov 03 Oct '07

03 Oct '07

Hi. I've noticed that parsing XML that contains many entity references may cause CXML to eat up all available heap space and crash. This can be easily reproduced: (cxml:parse-rod (format nil "<xml>~{~a~}</xml>" (loop repeat 4000 collect "<p>zz")) (cxml-dom:make-dom-builder)) (tested on SBCL / Linux) Looking at the code, I've noticed that xml/xml-parse.lisp relies on the tail recursion a lot (though always having proper tail recursion is frankly speaking somewhat dubious expectation when working with Common Lisp). What's worse, P/CONTENT function is non-tail-recursive when an entity reference is encountered, and this is exactly the cause of aforementioned crash. I've attached the patch which helped me solve the problem (it's made against cxml-2007-08-05). I've just noticed that recurse-on-entity returns NIL most of time and used that fact to cut off most of recursion. As of now my brain is somewhat foggy due to continuing coding race, so I didn't learn what recurse-on-entity actually does and how often can it return a non-NIL value. Overall I don't think this is a proper solution, most likely xml-parse.lisp needs some serious rework to make it more reliable. But I think at least this hack will help in most cases. Ivan

2 1

[cxml-devel] CXML vs usocket
by Magnus Henoch 29 Aug '07

29 Aug '07

I'm trying to use CXML, specifically the Klacks parser, to read streaming XML from a network socket (I'm writing a Jabber library), but I'm having problems with buffering. I'm using this code for testing: (defun cxml-test (host port &key (buffering nil)) (let ((socket (usocket:socket-connect host port :element-type '(unsigned-byte 8)))) (cxml:make-source (usocket:socket-stream socket) :buffering buffering :pathname "foo"))) And then I run (klacks:consume src) repeatedly. On the sending end, I use "nc -l -w 5 -p 42000", either typing in XML by hand or by redirecting a real XML file to netcat. With buffering enabled, this basically works. However, I need to process "stanzas" (Jabber term for complete elements that are children of the root element) as soon as they come in, not when the buffer is full or when the stream or the root element is closed. But when I disable buffering, I get (using CLISP from recent CVS): AREF: index 1 for #(60) is out of range [Condition of type SIMPLE-TYPE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [CLOSE-CONNECTION] Close SLIME connection Backtrace: [ SLIME parts skipped ] 5: INVOKE-DEBUGGER 6: AREF 7: REPLACE 8: #<COMPILED-FUNCTION #:|257 305 (DEFMETHOD XSTREAM-UNDERFLOW (#) ...)-25-1-1|> 9: CXML:MAKE-SOURCE 10: CXML:MAKE-SOURCE 11: (CXML:MAKE-SOURCE (USOCKET:SOCKET-STREAM SOCKET) :BUFFERING BUFFERING :PATHNAME "foo") 12: LET 13: (CXML-TEST '"localhost" '42000 ':BUFFERING 'NIL) SBCL 1.0.8.46 gets a similar error: The bounding indices 0 and 2 are bad for a sequence of length 1. [Condition of type SB-KERNEL:BOUNDING-INDICES-BAD-ERROR]See also: Common Lisp Hyperspec, bounding index designator [glossary] Common Lisp Hyperspec, SUBSEQ-OUT-OF-BOUNDS:IS-AN-ERROR [issue] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (SB-IMPL::SIGNAL-BOUNDING-INDICES-BAD-ERROR #(60) 0 2) 1: (SB-IMPL::SIGNAL-BOUNDING-INDICES-BAD-ERROR #(60) 0 2) 2: ((SB-PCL::FAST-METHOD RUNES::XSTREAM-UNDERFLOW (RUNES:XSTREAM)) #<unavailable argument> #<unavailable argument> #<RUNES:XSTREAM [main document :MAIN file://+/home/foo]>) 3: (CXML:MAKE-SOURCE #<RUNES:XSTREAM [main document :MAIN file://+/home/foo]>) 4: (NIL) 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SETF SRC (CXML-TEST "localhost" 42000 :BUFFERING NIL)) #<NULL-LEXENV>) It would be nice if this worked, and if additionally KLACKS:PEEK would do a non-blocking read. Magnus

2 2

[cxml-devel] (no more) spam
by David Lichteblau 29 Aug '07

29 Aug '07

Belatedly, apologies for the recent spam on cxml-devel. My own spam filter caught most of it, so I did not notice what was going on. Mailman's default setting on common-lisp.net for accept_these_members was to accept mails appearing to come from common-lisp.net members, including junk addresses like BlogBlaster(a)common-lisp.net. I have now disabled this mailman option for cxml-devel. d.

1 0

[cxml-devel] "How would you like to have your ad on 2 Million Websites ?"
by BlogBlaster＠common-lisp.net 26 Aug '07

26 Aug '07

1 0

[cxml-devel] How would you like unlimited hits to your website 15 minutes from now ?
by Hit-Booster＠common-lisp.net 25 Aug '07

25 Aug '07

New Break-through Automation Technology WILL Pull in hordes of Within 15 minutes you will have your own website traffic generator that will bring in an ever increasing amount of hits to your websites! Automatically This software is perfect for bringing real traffic to your site... even if... it's an affiliate link where you have no control over the website content! Using my automated program I have developed, just insert your url... ...choose a category... ...have HIT-BOOSTER send thousands of targeted visitors to your site. Let me tell you what Hit-Booster can do for you ...Hit-Booster will start sending hits to your website instantly at $0 cost to you! ...No matter what you are selling or offering - HIT BOOSTER will pull in hordes of potential customers to your website or affiliate website! ...sets this up completely for you on Auto-Pilot! ...Use it for all of your websites - there is no limit . ...Receive my personal support and email address with your purchase so I can help you to succeed! ...your web site will quickly achieve Ultra High Link Popularity on the Major Search Engines ...you'll get 1000's of Highly Targeted visitors to your web site or affiliate web site overnight ...many are getting more Customers and Sales than they can handle For Full Details please download the attached .html file Unsubscribe Please read the attached .txt file

1 0

[cxml-devel] How would you like an extra $500 - $1000 a week with 15 minutes of your time ?
by Work＠common-lisp.net 24 Aug '07

24 Aug '07

1 0

[cxml-devel] Can you afford to lose 300, 000 potential customers per year ?
by Instant＠common-lisp.net 22 Aug '07

22 Aug '07

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel