1 |
joko |
1.1 |
@sequence meta |
2 |
|
|
@title joko's sample notes - 2003-03 - ResourceIntegration |
3 |
|
|
@subtitle ResourceIntegration II |
4 |
|
|
@topic joko's Tasks |
5 |
|
|
@author joko@netfrag.org |
6 |
|
|
@document-mime-type text/plain |
7 |
|
|
@document-mime-type text/english text/german |
8 |
|
|
@document-mime-type text/vnd.twingle |
9 |
|
|
|
10 |
|
|
@sequence meta |
11 |
|
|
@document-history |
12 |
|
|
@cvs-info |
13 |
joko |
1.2 |
$Id: joko_2003-03.twingle,v 1.1 2003/03/06 22:34:20 joko Exp $ |
14 |
|
|
$Log: joko_2003-03.twingle,v $ |
15 |
|
|
Revision 1.1 2003/03/06 22:34:20 joko |
16 |
|
|
+ initial commit |
17 |
|
|
|
18 |
joko |
1.1 |
|
19 |
|
|
@sequence meta |
20 |
|
|
@x-transport |
21 |
|
|
@x-transport-from grasshopper.netfrag.org |
22 |
|
|
@x-transport-to quepasa.netfrag.org |
23 |
|
|
@x-transporter Microsoft Windows |
24 |
|
|
@x-transporter WinCVS [WinCVS 1.3.8.1 Beta 8 (Build 1)] |
25 |
|
|
@x-transporter-protocol cvs client-server protocol |
26 |
|
|
@x-transporter OpenSSH client on grasshopper [OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f] |
27 |
|
|
@x-transporter-protocol ssh [OpenSSH Version 2] |
28 |
|
|
@x-transporter OpenSSH daemon on quepasa [OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f] |
29 |
|
|
@x-transporter cvs [Concurrent Versions System (CVS) 1.11.1p1 (client/server)] |
30 |
|
|
@x-transporter-protocol cvs client-server protocol |
31 |
|
|
@x-transporter Linux running on quepasa.netfrag.org [Linux version 2.4.18-29um (root@linux) (gcc version 2.95.3 20010315 (SuSE)) #1 Sun May 26 17:01:48 CEST 2002] |
32 |
|
|
@x-transporter-protocol ext3 |
33 |
|
|
@x-transporter Linux running on h1.service.netfrag.org [Linux version 2.4.10-4GB (root@Pentium.suse.de) (gcc version 2.95.3 20010315 (SuSE)) #1 Tue Sep 25 12:33:54 GMT 2001] |
34 |
|
|
@x-transporter-protocol ext3 |
35 |
|
|
#@x-converter twingle [Twingle 0.01 - http://search.netfrag.org/twingle] |
36 |
|
|
|
37 |
|
|
@sequence script |
38 |
|
|
@set o=@todo |
39 |
|
|
|
40 |
|
|
|
41 |
|
|
|
42 |
|
|
@sequence block |
43 |
|
|
@injected |
44 |
|
|
@date 2003-03-06 20:29 |
45 |
|
|
@file [unknown] |
46 |
|
|
@x-editor Notepad [Microsoft Editor Version 5.0 (Build 2195: Service Pack 3) |
47 |
|
|
@x-transporter Microsoft COM |
48 |
|
|
@x-transporter-protocol copy & paste negotiation |
49 |
|
|
@x-editor UltraEdit [UltraEdit(r)-32 Professional Text/HEX Editor Version 8.10b] |
50 |
|
|
|
51 |
|
|
|
52 |
|
|
o use arial|verdana for netscape|mozilla rendering on netfrag.org |
53 |
|
|
|
54 |
|
|
- We get spam! |
55 |
|
|
After feeling relatively safe through amavis based email filtering, it happened again. |
56 |
|
|
jonen recieved some spam again. |
57 |
|
|
|
58 |
|
|
Why? |
59 |
|
|
I believe the addresses get collected by foreign agents crawling |
60 |
|
|
the growing content on netfrag.org. |
61 |
|
|
|
62 |
|
|
What todo now? |
63 |
|
|
Mungle email addresses published on netfrag.org through some lisp- |
64 |
|
|
or scheme-based address-mungler found recently. |
65 |
|
|
They stay rfc-compliant, but are (hopefully) unreachable for common |
66 |
|
|
regex parsers. |
67 |
|
|
Send info to ->jonen. |
68 |
|
|
@tbd Automate this task! Do you wanna rewrite each address by hand...??? |
69 |
|
|
|
70 |
|
|
o personal requirement: |
71 |
|
|
o daily: review contributions made by other users |
72 |
|
|
o requirement to solve this: have everything as rss/rdf and filter the xml by author |
73 |
|
|
|
74 |
|
|
o rss.netfrag.org (register) |
75 |
|
|
o establish some web-based rss-browser embedding content from |
76 |
|
|
o RssGenerators for local content ... |
77 |
|
|
o news//rss (for news.netfrag.org) |
78 |
|
|
o cvs//rss (for cvs.netfrag.org) |
79 |
|
|
o ... and RssGateways to other ones, possibly at remote locations |
80 |
|
|
o phpWiki//rss (for www.netfrag.org) |
81 |
|
|
o TWiki//rss (for future www.netfrag.org) |
82 |
|
|
|
83 |
|
|
o post to perl-development (nfo.dev.perl): |
84 |
|
|
o how to abstract the view/editing of xml-files via an api? |
85 |
|
|
o fetch: all|single-node |
86 |
|
|
o edit: single-node flattened into an object |
87 |
|
|
o browser layer: locator registry (pointing to a) an orm-db and b) to a file-set of xml-files (our control-db)) |
88 |
|
|
o item layer: view/edit nodes of an xml-file a) in a tree-editor (look at HTML_Tree_XYZ itself!!!) and |
89 |
|
|
b) split into our "flat-components" Item and List (object-like) |
90 |
|
|
|
91 |
|
|
how b)? solve in backend! |
92 |
|
|
o backend |
93 |
|
|
o change values containing references to their interpolated placeholders to convert a node to an item |
94 |
|
|
->getNode(...) |
95 |
|
|
example: getNode('root') |
96 |
|
|
o place querying api via XPath parallel to that -> also returns a single node or multiples (a node-set) |
97 |
|
|
->getNodeSet(...) |
98 |
|
|
example: getNodeSet('xpath-query|named-filter') |
99 |
|
|
o establish backend querying api for xml-documents on top of that! |
100 |
|
|
->sendQuery(...) should dispatch to one of ->getNode or ->getNodeSet |
101 |
|
|
o frontend |
102 |
|
|
o browse relations (parent-, child-node) using the ValueInterpolator and the ItemComponent |
103 |
|
|
o edit Attributes and Content of Nodes with the ItemComponent showing *two* areas (this is the "FlatteningOfNodes"): |
104 |
|
|
o -> attributes |
105 |
|
|
o -> content |
106 |
|
|
That's the way various XML-EasyTree-Xyz implementations use to work. |
107 |
|
|
@link http://www.cpan.org/ |
108 |
|
|
o frontend issues these generic rpc-commands to the backend (encapsulated somewhere) |
109 |
|
|
o ->sendQuery(array(remote=1, rpc=1, blah=1, $query )) - |
110 |
|
|
which gets dispatched by switching some stuff from "$query" to these methods under the hood (in fact, *implemented at backend side*) |
111 |
|
|
o ->getNodeSet('xpath-query|named-filter') |
112 |
|
|
example: |
113 |
|
|
$xml_filter_query = array( 'return' => 'object|object-set', [filter => 'xpath-query|named-filter'] ); |
114 |
|
|
(speak: Item or List) |
115 |
|
|
sendQuery(array(remote=1, rpc=1, blah=1, $xml_filter_query , xml=1??? )) - |
116 |
|
|
|
117 |
|
|
--> what is 'remote' and/or 'rpc' about??? |
118 |
|
|
if i remember that right - 'remote' means 'orm' (the datasource-type) and 'rpc' means 'rpc' (the transport-type) |
119 |
|
|
|
120 |
|
|
o new twingle-symbol-topology using ... |
121 |
|
|
<code> |
122 |
|
|
o ... @-tags (stolen from JavaDoc via phpDocumentor) |
123 |
|
|
o @-tags only refer to scopes they live in |
124 |
|
|
o make the basic work: @todo, @link, @see, etc. (but enhanced - of course - since perl doesn't limit you in any way....!!!) |
125 |
|
|
o add some more: @sequence, @is-a, @title |
126 |
|
|
o @see |
127 |
|
|
o @embed this-and-that from these .twingle files: |
128 |
|
|
o @link DummyNamespaces in PHP - final proposal.twingle |
129 |
|
|
o @link Re - Namespaces in PHP.twingle |
130 |
|
|
</code> |
131 |
|
|
|
132 |
|
|
o project-metadata: / nfo topics |
133 |
|
|
<code> |
134 |
|
|
@is-a rfc |
135 |
|
|
@todo tbd |
136 |
|
|
x @topic source(cvs) |
137 |
|
|
x @topic doc(api) |
138 |
|
|
o @topic source(raw) (via symlinks: expand directories first, symlink files afterwards!) |
139 |
|
|
o @topic doc(tutorial) |
140 |
|
|
o @topic doc(examples) |
141 |
|
|
o @topic doc(howto) |
142 |
|
|
o introduce: @subtopic: |
143 |
|
|
@topic source |
144 |
|
|
@subtopic raw|cvs |
145 |
|
|
@topic doc |
146 |
|
|
@subtopic api|tutorial|examples|howto |
147 |
|
|
</code> |
148 |
|
|
|
149 |
|
|
o register: api.netfrag.org |
150 |
|
|
|
151 |
|
|
o arcor!!! |
152 |
|
|
|
153 |
|
|
o working alpha version of "Ts" on new server niu!!! |
154 |
|
|
|
155 |
|
|
o .phpdocrc: split main code to module, integrate index-generation of predefined (registered) modules |
156 |
|
|
|
157 |
|
|
o RssNewsletter: |
158 |
|
|
o schedule |
159 |
|
|
o hourly, daily, weekly, monthly, on-incoming |
160 |
|
|
o choose topic |
161 |
|
|
o all topics (cvs, news, api, docs, www) |
162 |
|
|
o choose destination |
163 |
|
|
o filtered-rss made available at specified url as xml or xhtml |
164 |
|
|
o via email |
165 |
|
|
o archived in archive-type (zip|tar) with format (html|) |
166 |
|
|
made available at specified url |
167 |
|
|
|
168 |
|
|
o look at FreeBSD's "doscmd"!!! |
169 |
|
|
|
170 |
|
|
o mechanism to refactor old smtp-mail-messages into new nntp-news-posts |
171 |
|
|
all our tools fail! *forwarding* the message seems to break mime (for e.g. the mozilla-viewer and probably others) |
172 |
|
|
o possible solution: strip "--- forwarded by ---" - header before actually posting |
173 |
|
|
maybe identifiable by subject: [Fwd: ] |
174 |
|
|
|
175 |
|
|
o enhance Twingle: |
176 |
|
|
o twingle2message: |
177 |
|
|
o twingle2mail: twingle2rfc822, twingle2mime |
178 |
|
|
o twingle2news: twingle2rfc |
179 |
|
|
|
180 |
|
|
o gather version info from installed components: |
181 |
|
|
o CPAN |
182 |
|
|
o PEAR |
183 |
|
|
x GNU: <program> --version (e.g.: cvs --version) |
184 |
|
|
x OpenSSH: ssh -V |
185 |
|
|
x Linux: cat /proc/version |
186 |
|
|
o our Perl-/PHP- component system |
187 |
|
|
|
188 |
|
|
o what are the MIME-types of XML-payloads sent between (e.g.) RPCXML-hosts??? |
189 |
|
|
text/xml??? |
190 |
|
|
|
191 |
|
|
look at /etc/mime.types!!! |
192 |
|
|
e.g.: (stripped from there) - looking interesting: |
193 |
|
|
|
194 |
|
|
text/* |
195 |
|
|
text/x-java |
196 |
|
|
text/uri-list |
197 |
|
|
text/rfc822-headers |
198 |
|
|
text/directory |
199 |
|
|
text/vnd.IPTC.NewsML |
200 |
|
|
text/vnd.IPTC.NITF |
201 |
|
|
text/vnd.motorola.reflex |
202 |
|
|
text/vnd.DMClientScript |
203 |
|
|
text/richtext |
204 |
|
|
text/rtf |
205 |
|
|
text/plain |
206 |
|
|
text/comma-seperated-values |
207 |
|
|
text/css |
208 |
|
|
text/enriched |
209 |
|
|
|
210 |
|
|
--> vnd=vendor??? |
211 |
|
|
|
212 |
|
|
@sequence references |
213 |
|
|
@title The text/enriched MIME Content-type |
214 |
|
|
@link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1896.html |
215 |
|
|
@title Mechanisms for Specifying and Describing the Format of Internet Message Bodies |
216 |
|
|
@link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1521.html |
217 |
|
|
@title The text/enriched MIME Content-type |
218 |
|
|
@link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1523.html |
219 |
|
|
@title Mechanisms for Specifying and Describing the Format of Internet Message Bodies |
220 |
|
|
@link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1341.html |
221 |
|
|
@title The text/enriched MIME Content-type |
222 |
|
|
@link http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1563.html |
223 |
|
|
|
224 |
|
|
message/delivery-status |
225 |
|
|
message/disposition-notification |
226 |
|
|
message/external-body |
227 |
|
|
message/http |
228 |
|
|
message/s-http |
229 |
|
|
message/news |
230 |
|
|
message/partial |
231 |
|
|
message/rfc822 |
232 |
|
|
|
233 |
|
|
inode/chardevice |
234 |
|
|
inode/blockdevice |
235 |
|
|
inode/directory-locked |
236 |
|
|
inode/directory |
237 |
|
|
inode/fifo |
238 |
|
|
inode/socket |
239 |
|
|
|
240 |
|
|
multipart/* |
241 |
|
|
|
242 |
|
|
o refactor some twingle tags using ETF: |
243 |
|
|
@link http://citeseer.nj.nec.com/borenstein94textenriched.html |
244 |
|
|
--- snip --- |
245 |
|
|
@misc{ borenstein-textenriched, |
246 |
|
|
author = "N. Borenstein", |
247 |
|
|
title = "The text/enriched MIME Content-type", |
248 |
|
|
url = "citeseer.nj.nec.com/borenstein94textenriched.html" } |
249 |
|
|
--- snip --- |
250 |
|
|
|
251 |
|
|
o re-enable yakka! |
252 |
|
|
@link http://netfrag.org/~bareface/yakka/ |
253 |
|
|
|
254 |
|
|
o search.netfrag.org |
255 |
|
|
o enable mnoGoSearch to index http://www.netfrag.org/docs/code/api/ |
256 |
joko |
1.2 |
|
257 |
|
|
o post xml-via-rpc-querying proposal from above to nfo.dev.perl and cc to jonen! |
258 |
|
|
|
259 |
|
|
o enhancement for Twingle AutoLink LinkInterpolation: |
260 |
|
|
o don't resolve namespace identifiers (e.g. 'Data::Storage') against |
261 |
|
|
global search.netfrag.org/Search::This::Namespace |
262 |
|
|
o query namespaced links against an organization-wide (custom) NamespaceRegistry before!!! |
263 |
|
|
o use mysql/Tangram? |
264 |
|
|
o use xml? |
265 |
|
|
o just fallback to "GlobalSerchMode" if nothing was found in the step before! |
266 |
|
|
o Data::Storage will directly be resolved to this url or tag afterwards: |
267 |
|
|
@link http://www.netfrag.org/docs/topics/perl-libs/Data-Storage.html |
268 |
|
|
and not to |
269 |
|
|
@link http://www.netfrag.org/search/?q=Data::Storage&o=1&ul=/ |
270 |
|
|
like it was before! |
271 |
|
|
|
272 |
|
|
|
273 |
joko |
1.1 |
|