406 |
|
|
407 |
o google::[outlook ldap] |
o google::[outlook ldap] |
408 |
|
|
409 |
|
o search::LDAP Search Error |
410 |
|
|
411 |
|
o nice layout: http://depts.washington.edu/cac/cchome/mis.html |
412 |
|
|
413 |
|
o split up custom gui: |
414 |
|
o two parts (topics): "notes" & "ideas" (& "visions"?) |
415 |
|
o *both* may have contexts (are associated with one or more other arbitrary items) |
416 |
|
o these may be StartingPoints when having a number of things cross referenced |
417 |
|
|
418 |
|
o [search::some news posts got purged, sorry] |
419 |
|
|
420 |
|
o [search::quepasa moves slow] |
421 |
|
|
422 |
|
o mail output from "df" at quepasa.netfrag.org |
423 |
|
|
424 |
|
o tell rabit about ps-lxr (lxr-ps?) (the ps filter and link-expander) |
425 |
|
|
426 |
|
o search::Business::OnlinePayment |
427 |
|
|
428 |
|
o enhance CVSSpam's ruby-scanner's keywords (TODO, FIXME, etc.) |
429 |
|
o REVIEW |
430 |
|
o think about different mechanism of how to say "to this with that" to 'cvsspam.rb' |
431 |
|
o couple 'cvsspam.rb' and the not-yet-ready |
432 |
|
link-expansion/item-interpolation WebService on quepasa.netfrag.org |
433 |
|
o filter incoming content through that! forward via mail afterwards! |
434 |
|
|
435 |
|
o do the same thing described above with inn: |
436 |
|
o couple the inn-perl-filters with the mentioned InterpolWebService ;-) |
437 |
|
o or should we name it "ExtrapolWebService"? |
438 |
|
|
439 |
|
o hehe: search::interpol |
440 |
|
|
441 |
|
o search::it's too hard |
442 |
|
|
443 |
|
x what's new in perl 5.8.0? |
444 |
|
x Unicode |
445 |
|
x Threads |
446 |
|
x IO |
447 |
|
x Signals |
448 |
|
x Speed |
449 |
|
|
450 |
|
o use WWW::Mechanize!!! |
451 |
|
|
452 |
|
o compare DesignPattern::Bridge with Class::Inner! |
453 |
|
|
454 |
|
o refactor the DesignPattern::-namespace to the Class::-namespace (perl & php!)!!! |
455 |
|
|
456 |
|
o have seperated search-spaces for |
457 |
|
o nfoweb & co. |
458 |
|
o news |
459 |
|
o cvs-logs |
460 |
|
o .... but: still let the feature to search the whole index ... |
461 |
|
|
462 |
|
o EasyDoc??? |
463 |
|
x occupied: look at htmltmpl.sourceforge.net |
464 |
|
x it's for python *and* php!!! |
465 |
|
|
466 |
|
o search::OpenAccess it's already occupied - it's odbc driver stuff |
467 |
|
|
468 |
|
x why not rdf right now? |
469 |
|
x search::[RDF -- the reason given usually being "it's too hard."] |
470 |
|
|
471 |
|
o search::syncml |
472 |
|
|
473 |
|
x search::perl inner class |
474 |
|
x it works! |
475 |
|
x the intended document is found on first place |
476 |
|
x this document is also found |
477 |
|
o just try to strip out the two documents found in between, |
478 |
|
these are the newsportal overview-pages (ThreadView) |
479 |
|
where the keywords are found inside the pure titles |
480 |
|
|
481 |
|
x DSMLv2: |
482 |
|
from http://www.netfrag.org/webnews/article.php?id=241&group=nfo.links.computing |
483 |
|
DSMLv2 is defined in terms of a set of XML fragments that are used as |
484 |
|
payloads in a binding. A binding defines how the DSMLv2 XML fragments are sent |
485 |
|
as requests and responses in the context of a specific transport such as SOAP, |
486 |
|
SMTP, or a simple data file. DSMLv2 defines two normative bindings: (1) a SOAP |
487 |
|
request/response binding is defined in section 6; and (2) a file binding that |
488 |
|
serves as the DSMLv2 analog of LDIF is defined in section 7. The rules for |
489 |
|
defining other DSMLv2 compliant bindings are found in section 8. |
490 |
|
|
491 |
|
|
492 |
|
|
493 |
|
|