dataisland-developer Mailing List for The Dataisland Framework
Status: Alpha
Brought to you by:
varsenault
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(26) |
Jun
(15) |
Jul
(2) |
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Hugues B. <hug...@ho...> - 2012-05-30 18:53:08
|
Yo buddy, I'm so sorry we haven't kept in contact in a little while - but I wanted to share with you something REALLY awesome I discovered! I'm getting a comfortable side-income simply by doing surveys for major corporations that pay TONS to learn more about me and you so they know what to sell to us on the product shelves. I'm getting paid $25-$90 per survey, and a survey takes no more than 5 minutes to do! Plus you fill out these surveys from anywhere in the world you've wanted to go :) If you get approval, make sure to tell me - I'll send a list of the higher paid surveys! http://bit.ly/MKKDWZ Check for your spot ASAP or it'll get filled! Your buddy Hugues |
From: Hugues B. <hug...@ho...> - 2012-04-30 09:48:11
|
hey dataisland-developer@lists.sourceforge.net your just one click away from having anything you've ever wanted http://www.cnbc29i.com/ |
From: Hugues B. <hug...@ho...> - 2012-04-23 07:20:51
|
hey whats up partner my boss showed me this life changing kit it took all the worries out of my life to be honest with you Im currently earning $6,000 /month by setting up an online program and letting it run automatically also there were no risks in receiving the kit which is about $2 for shipping http://twurl.nl/ktscav Get your trial kit quick before they run out! your partner Hugues |
From: Vincent-Olivier A. <vi...@up...> - 2004-07-30 02:11:30
|
All=F4 =E0 tous! =C7a fait longtemps que j'ai donn=E9 des nouvelles sur D.I. =C7a ne veut=20 cependant pas dire qu'il ne se passe rien, par exemple! Comme vous le savez, je suis =E0 l'emploi de l'Agence Braque et depuis qu= e=20 j'y suis, je n'ai fait que travailler sur Data=EFsland, ou presque. D'ici= =20 vendredi prochain, j'aurai commis tout ce dont je pourrai sur le CVS=20 avec les instructions sur comment utiliser le tout. Voici o=F9 j'en suis=20 rendu... Un des aspects les plus importants de cette nouvelle version=20 c'est le MDA (model-driven architecture). C'est le principe selon=20 lequel, il faudrait qu'il soit possible de b=E2tir des applications au=20 complet seulement =E0 partir de leur mod=E8le UML (ou autre). Gr=E2ce =E0= =20 Fran=E7ois Eric, j'ai =E9t=E9 introduit aux merveilles de AndroMDA, un=20 framework qui "lit" le mod=E8le UML et qui, selon des templates Velocity,= =20 g=E9n=E8re le code voulu. Le principe du MDA se marie parfaitement =E0 Re= ST,=20 qui est la th=E9orie qu'aucune logique d'affaire, =E0 proprement parl=E9,= est=20 n=E9cessaire : toutes les op=E9rations possibles sur des objets se r=E9su= ment=20 aux op=E9rations HTTP de base : HEAD, GET, POST, PUT, DELETE. En partant=20 de ces deux id=E9es, nous avons fait un module MDA qui se charge de=20 g=E9n=E9rer (pour chaque classe UML) 1) le JavaBean _*localizable*_, anno= t=E9e=20 XDoclet pour Hibernate, 2) la fa=E7ade de logique de persistance=20 Hibernate, 3) les diverses exceptions aff=E9rentes =E0 la persistance=20 (ObjectNotFound, UnicityConstraintViolation, etc), 4) les actions struts=20 CRUD pour la liste, l'affichage formulaire, la sauvegarder, la=20 suppression, 5) les JSP struts pour aller avec les actions, 6) le=20 mapping JiBX qui permet de s=E9rialiser les instances de la classe en un=20 document XML et vice-versa. Et =E7a MARCHE!!!! Nous allons livrer la=20 semaine prochaine, pour Jetsgo, une application qui "wrappe" une vieille=20 base de donn=E9es et toute l'application est g=E9n=E9r=E9e avec ce syst=E8= me. Je=20 vais, dans les prochaines semaines, documenter tous ces beaux jouets=20 pour que vous puissiez tous les utiliser. Qu'en dites-vous? Je vous propose aussi un mode diff=E9rent pour le d=E9veloppement inspir=E9= de=20 Pierre-David... Je crois qu'il est plus simple que chacun de nous ait=20 son projet open source s=E9par=E9 et que nous commettions du code =E0 nos= =20 propres projets (et =E0 ceux des autres s'il y a besoin). De cette fa=E7o= n,=20 les droits et la direction technique sont plus simples =E0 d=E9terminer := le=20 responsable du projet et le propri=E9taire du code et c'est lui qui d=E9c= ide=20 ce qui va dans le code. J'ai not=E9 que de plus en plus de projets=20 opensource fonctionnent sur ce principe dit "darwinien". Les diff=E9rents= =20 projets se rencontrent en utilisant leurs APIs respectifs. Il suffit=20 donc de r=E9partir les t=E2ches selon les int=E9r=EAts de chacun. Plus ba= s, vous=20 trouverez, ma liste de shopping logiciel; c'est ce dont j'ai besoin, et=20 qui pourrait =EAtre d=E9velopp=E9 et pris en charge par l'un de vous... Q= u'en=20 dites-vous? Les objectifs pour la version 3.0 se fondent dans 3 grands axes : le Web=20 s=E9mantique, le MDA, et l'approche ReST. Vous savez tous ce qu'est Rest=20 et MDA. J'ai discut=E9 de l'axe s=E9mantique avec certains d'entre vous, = il=20 s'agit d'arriver =E0 ce que Data=EFsland devienne un "agent" personnel,=20 repr=E9sentant les usag=E9s (personnes et compagnies) sur le Web. Mis =E0= part=20 le CMS, qui est l'aspect publication du Web s=E9mantique, j'ai commenc=E9= =E0=20 concevoir un "robot" data=EFsland qui pourrait effectuer des t=E2ches de=20 repr=E9sentation =E0 partir des donn=E9es que quelqu'un publie sur son si= te=20 Web. Pour plus d'info l=E0-dessus, vous pouvez aller consulter mon blogue= =20 (www.up4.com) sur les conversations que j'ai avec les gens dans le=20 domaine. Je vais bient=F4t publier les requis pour cette partie du projet= . Ce qu'il me reste =E0 faire pour la version 3.0 * Refaire le "core" de Data=EFsland : il faut que je refasse les classes noyau du package org.dataisland. Notamment pour 1) Am=E9liorer la n=E9gociation de contenu conform=E9ment aux standard= s W3C, 2) refaire l'API de transmission SAX2 bidirectionnelle (pour sauver et g=E9n=E9rer les documents), 3) fournir la capacit=E9 de g=E9n=E9rer automatiquement une "sitemap" et un index de recherche = =E0 partir des m=E9tadonn=E9es pour chaque instance DataIsland 4) Revoi= r la s=E9rialisation pour supporter les nouvelles interfaces JAXP, 5) supporter toutes les op=E9rations HTTP GET/PUT/POST/DELETE/HEAD * Refaire l'ontologie "CMS" de Data=EFsland : il faut "merger" les templates MDA d=E9j=E0 faites avec Data=EFsland. * Ajouter des outils pour le s=E9mantique web : il faut ajouter, aux templates MDA, la g=E9n=E9ration de documents RSS, XSLT, RDF, FOAF, OWL, etc. * Support pour la r=E9tro-compatibilit=E9 des ontologies : quand une compagnie ou un individu met =E0 jour son mod=E8le UML et r=E9g=E9n= =E8re l'application, il faut pouvoir supporter que les interfaces supportent les ontologies pr=E9c=E9dentes, en faisant des op=E9rati= ons de diff=E9rences sur le mod=E8le et en proc=E9dant =E0 la transform= ation XSLT des diff=E9rentes versions (ie : il faut que si Mr X envoie =E0 Mr Y un document XML selon le DTD 1.0, Mr Y puisse le comprendre m=EAme s'il a install=E9 la version 2.0 de son DTD). * Data=EFsland-Agent : tout est =E0 faire pour =E7a. rester =E0 l'=E9= coute... Liste de shopping (dites-moi si =E7a vous int=E9resse) * Autodeploy (database schema adapter, ontology discovery, etc). Je crois que =E7a fait partie de tes choses, Pierre. * Gestion par JMX. Je crois que =E7a fait aussi partie de tes choses, Pierre. * Logging, statistiques. C'est un module qui permettrait de g=E9rer e= t d'analyser le traffic dataisland. * Data=EFsland Wiki. C'est un module qui permettrait d'h=E9berger du contenu wiki avec l'architecture dataisland. Il faut, par exemple, =EAtre en mesure d'importer TOUT le contenu de wikipedia (en.wikipedia.org) et de g=E9nerer le contenu en utilisant data=EFs= land. * Data=EFsland blog. Impl=E9mentation de blog en utilisant Dataisland= et Dataisland-CMS * Persisted resourcebundle. Utilitaire pour la gestion et la persistance du texte applicatif localis=E9 (genre "clickez ici", "sauvegarder", "submit", etc.) * Support pour la s=E9rialisation dans divers formats (SVG, XSL-FO, PDF, JPEG, RDF, etc) Bon, les gars, on se fait une petite bi=E8re bient=F4t pour discuter de =E7= a? Vincent |
From: Vincent-Olivier A. <vi...@up...> - 2004-06-29 03:09:06
|
You can see my working document @ http://dataisland.org/ This is just to show you the structure of the document. During the week, I will be including the UML diagrams (in SVG format) and the text. Vincent |
From: <rip...@ho...> - 2004-06-23 13:51:02
|
Hi ! Until now, I do not see any problem with the persistence. We should have enough freedom with Hhibernate. For now, I will wait for more real-world-examples to play with (examples based on the model that Vincent-Olivier sent me last week). pierre ----Original Message Follows---- From: Vincent-Olivier Arsenault <vi...@up...> Reply-To: dat...@li... To: dat...@li... Subject: [Dataisland-developer] Updates Date: Tue, 22 Jun 2004 09:16:53 -0400 MIME-Version: 1.0 Received: from sc8-sf-mx1.sourceforge.net ([66.35.250.206]) by mc11-f22.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 22 Jun 2004 06:18:03 -0700 Received: from sc8-sf-uberspam1-b.sourceforge.net ([10.3.1.6] helo=sc8-sf-uberspam1.sourceforge.net)by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:DES-CBC3-SHA:168)(Exim 4.30)id 1BclA3-00045Q-DEfor pj...@us...; Tue, 22 Jun 2004 06:18:03 -0700 Received: from projects.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7])by sc8-sf-uberspam1.sourceforge.net (Postfix) with ESMTP id 7B3EC1D14C4for <pj...@us...>; Tue, 22 Jun 2004 06:18:03 -0700 (PDT) Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.12] helo=sc8-sf-mx2.sourceforge.net)by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30)id 1Bcl94-0007nr-26for dat...@li...; Tue, 22 Jun 2004 06:17:02 -0700 Received: from falla.videotron.net ([205.151.222.106])by sc8-sf-mx2.sourceforge.net with esmtp (Exim 4.30)id 1Bcl92-0000gr-Dkfor dat...@li...; Tue, 22 Jun 2004 06:17:00 -0700 Received: from [10.10.10.204] ([207.253.219.30]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0HZ...@fa...> for dat...@li...; Tue, 22 Jun 2004 09:16:54 -0400 (EDT) X-Message-Info: JGTYoYF78jHSui20u1WWCmXsTN25DwG9 Message-id: <40D...@up...> User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502) X-Accept-Language: en-us, en X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=2000010.0 SF_CHICKENPOX_MINUS BODY: Text interparsed with -0.0 SF_CHICKENPOX_APOSTROPHE BODY: Text interparsed with '0.0 SF_CHICKENPOX_PERIOD BODY: Text interparsed with .0.0 SF_CHICKENPOX_PLUS BODY: Text interparsed with + Errors-To: dat...@li... X-BeenThere: dat...@li... X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/dataisland-developer>,<mailto:dat...@li...?subject=unsubscribe> List-Id: <dataisland-developer.lists.sourceforge.net> List-Post: <mailto:dat...@li...> List-Help: <mailto:dat...@li...?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/dataisland-developer>,<mailto:dat...@li...?subject=subscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=dataisland-developer> X-Original-Date: Tue, 22 Jun 2004 09:16:53 -0400 X-Spam-Score: 0.1 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=2000010.0 SF_CHICKENPOX_SLASH BODY: Text interparsed with /0.0 SF_CHICKENPOX_MINUS BODY: Text interparsed with -0.0 SF_CHICKENPOX_AT BODY: Text interparsed with @0.0 SF_CHICKENPOX_APOSTROPHE BODY: Text interparsed with '0.0 SF_CHICKENPOX_PERIOD BODY: Text interparsed with .0.0 SF_CHICKENPOX_PLUS BODY: Text interparsed with + Return-Path: dat...@li... X-OriginalArrivalTime: 22 Jun 2004 13:18:03.0773 (UTC) FILETIME=[595CAAD0:01C4585B] Hi all, Before the end of the month (that is next week), there will be an updated home page for dataisland.org. It will be the main architectural reference as Dataïsland 3.0 comes to life. I will let you know as soon as I post the first draft. This document will keep a draft status until we all feel it's worth feature-freezing, which I estimate will happen around August 1rst. Right now, I'm reading a lot on RDF, XSDL, DAML+OIL, and other W3C stuff, to make sure we have pretty much everything covered. Vincent PS: Pierre, can you give an update on your persistence tests. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Dataisland-developer mailing list Dat...@li... https://lists.sourceforge.net/lists/listinfo/dataisland-developer _________________________________________________________________ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ |
From: Vincent-Olivier A. <vi...@up...> - 2004-06-22 13:17:02
|
Hi all, Before the end of the month (that is next week), there will be an= =20 updated home page for dataisland.org. It will be the main architectur= al=20 reference as Data=EFsland 3.0 comes to life. I will let you know as s= oon=20 as I post the first draft. This document will keep a draft status unt= il=20 we all feel it's worth feature-freezing, which I estimate will happen= =20 around August 1rst. Right now, I'm reading a lot on RDF, XSDL, DAML+OIL, and other W3C= =20 stuff, to make sure we have pretty much everything covered. Vincent PS: Pierre, can you give an update on your persistence tests. |
From: Vincent-Olivier A. <vi...@up...> - 2004-06-01 22:58:05
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Yo,<br> <br> I have looked briefly at your framework's code and I think we should meet to discuss it. Here is how I think it should integrate with the Dataïsland-CMS framework :<br> <br> The CMSDataïsland class will somehow extend your main service class (I can't have access to the CVS right now, so I don't know exactly the name). And given that your framework handles :<br> <ul> <li>Ontology discovery</li> <li>User management, authentication and security</li> <li>Object persitence</li> </ul> , then the CMSDataïsland dataïsland will handle :<br> <ul> <li>the HTTP interfacing</li> <li>the bidirectionnal request processing and dispatching and responding (for CRUD and listing operations)</li> <li>the GUI and document generation (XSLT tranformation, form generation, etc.)</li> <li>the content negociation (resource, locale, document type)</li> <li>the object to XML mapping</li> </ul> Is that about right? I need to hear more from you so I can better understand how we will all do that. Can we meet next week (not monday)?<br> <br> Thanks,<br> <br> Vincent<br> <br> </body> </html> |
From: Vincent-Olivier A. <vi...@up...> - 2004-05-22 17:01:49
|
Yeeehaaw! It is an immense honor for me to officially open the Data=EFsland 3.0=20 development cycle. This message is both a call to participation and a=20 brief explanation of what D=EF 3.0 is about. The people that registered to this list are : Sergei Rybakov (artefficient) : interface architect Saad Tazi (saadtazi) : developper Hugues Brunelle (zieram) : graphic designer Pierre-David Belanger (pjer) : developper Vincent-Olivier Arsenault (varsenault) : developper I would like everybody to participate, but if you do not wish to be=20 bothered, just let me know and I will remove you from this annoying=20 list. ;-) What the fuck is Data=EFsland 3.0 ? If you have no clue on what Data=EFsland is and you want to participate,=20 just call me and I'll personally explain to you. But for most (all?) of=20 you, the basics are well understood. So, I'll just go on with the=20 specifics of the 3.0 version. There are 6 objectives. Code intellectual ownership : it's all yours First, to whom does the Data=EFsland code belong? That is a very importan= t=20 question for which we will need to figure out an answer. Of course the=20 license is LPGL, but any licensing scheme, even GPL needs a specified=20 owner to be enforced. I suggest this : all the source equally belongs to=20 all the developpers that participate to its production, in alphabetical=20 order. Ex : Data=EFsland 3.0 =A92004 Vincent-Olivier Arsenault, Pierre-Da= vid=20 Belanger, Hugues Brunelle, Pierre-David Belanger, Sergei Rybakov, Saad=20 Tazi. Simple. What do you think? Strengtening the architecture : tightening ReST idiomatic BiDi paradigms and enforcing modularity Dataisland has been thought from the beginning as a bidirectional XML=20 object brokering system using ReST=20 <http://internet.conveyor.com/RESTwiki/moin.cgi/FrontPage> as its=20 internet interface. Although the rendering engine (read) is pretty=20 complete, the data acquisition part (create, update, delete) has been=20 implemented very recently and therefore is a little flaky. Also, as the=20 ReST architectural principle is gaining momentum, its requirements got=20 refined as well. The Data=EFsland must become the most compliant ReST=20 implementation available! As we were getting clients to use Data=EFsland, we kept adding business=20 specific code here and there. For version 3.0, we will clean all that=20 and separate modules in this way : * *dataisland* : this is the core architectural package. This is the ReST implementation, concerned only of implementing an HTTP-like object API for localization and content negotiation, etc. * *dataisland-cms* : this is a content management system implemented in a ReSTful way, using the dataisland core package. This will merely be a wrap for Pierre's PJER-CMS project <https://sourceforge.net/projects/pjer-cm/>. This contains security features such as user management and authentication mechanisms. It also has nifty features such as : automatic ontology discovery, persistence, etc. * *opencommerce* : this is the ecommerce buildup extension for dataisland-cms. It adds ecommerce capabilities like basket, checkout and other CRM-like features. * *buzzcut* : it's the "cultural" industry extension for opencommerce. It adds artist, event, and work (album, concert, etc.) management. * *intelligenzia* : it's the NGO package building up on the dataisland-cms. It's like a "power to the people" system that allows NGOs to better organize themselves. GUI auto generation Somehow, Sergei and Hugues, have to come up with an algorithm that will=20 automatically generate a (usable) GUI from an ontology (XML or SQL=20 schema). That is, if you know an artist has a name, a birthday, etc.,=20 you should be able to know what interface you need to create, update and=20 delete an artist instance. Code delegation : let's not re-invent the wheel, ok? For better and distributed code maintenance, we should not write code=20 for which a usable library already exists. For example, Pierre has=20 written a nice abstract content management framework that takes care of=20 authentication, object storage, and all. We would be stupid not to use=20 it, right? Well, the data=EFsland code has been around for almost 5 years= =20 now, and some part of it have been implemented elsewhere (almost always=20 in a better way, and sometimes even in the standard Java libraries),=20 well we have to migrate to use that code instead. An example of this is=20 the org.dataisland.URI class. Supporting code generation (MDA) and metadata programming Ideally, the opencommerce, buzzcut and intelligenzia packages will only=20 be a UML model that we use to generate the code necessary to make a=20 fully functional application out of it. We will build up on the AndroMDA=20 <http://www.andromda.org/> and XDoclet <http://xdoclet.sourceforge.net/>=20 projects and see what we can do with that. Now what is coming up This week, I will get in touch with all of you to see what you think and=20 if you are interested. Also, I will post architecture document for you=20 to comment on. It will be fun!! Have a nice weekend. v-o |
From: <ben...@id...> - 2004-05-22 13:56:25
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Vincent-Olivier A. <vi...@up...> - 2003-09-12 14:48:18
|
UI, of course! Mais c'est le travail de recherche qui est long...!! v-o Saad Tazi wrote: >Coucou Vincent: >Advocacy:=20 >- pour RH CMM,=20 >=09standard: Log4j, Ant, Xalan, Xerces, Lucene, and Junit >=09template: xslt ou jps >voila ce qui me vient, il faut continuer =E0 creuser pour completer = ce >tableau >-----Original Message----- >From: dat...@li... >[mailto:dat...@li...] On Behalf = Of >Vincent-Olivier Arsenault >Sent: September 11, 2003 9:23 PM >To: dat...@li... >Subject: [Dataisland-developer] Maven-Generated Site Is Now Live > >See : dataisland.org > >Vincent-Olivier > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Dataisland-developer mailing list >Dat...@li... >https://lists.sourceforge.net/lists/listinfo/dataisland-developer > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Dataisland-developer mailing list >Dat...@li... >https://lists.sourceforge.net/lists/listinfo/dataisland-developer > =20 > |
From: Saad T. <st...@sy...> - 2003-09-12 14:09:03
|
Coucou Vincent: Advocacy:=20 - pour RH CMM,=20 standard: Log4j, Ant, Xalan, Xerces, Lucene, and Junit template: xslt ou jps voila ce qui me vient, il faut continuer =E0 creuser pour completer ce tableau -----Original Message----- From: dat...@li... [mailto:dat...@li...] On Behalf Of Vincent-Olivier Arsenault Sent: September 11, 2003 9:23 PM To: dat...@li... Subject: [Dataisland-developer] Maven-Generated Site Is Now Live See : dataisland.org Vincent-Olivier ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dataisland-developer mailing list Dat...@li... https://lists.sourceforge.net/lists/listinfo/dataisland-developer |
From: Vincent-Olivier A. <vi...@up...> - 2003-09-12 01:23:15
|
See : dataisland.org Vincent-Olivier |
From: Vincent-Olivier A. <vi...@up...> - 2003-09-11 19:04:03
|
Hello, See my embedded comments... v-o Saad Tazi wrote: >Questions: >[Saad Tazi] New BUGS text with standard compliance, runtime, performance > >and algorithmic known issues text: is it just a text file containing >list of bugs? > Yes. Those that you know of. >[Saad Tazi] New INSTALL text with infrastructure requirements and >installation procedures: done in html. I just have to convert html to >text, haven't I? > No, leave it in XHTML and put it in --> doc/install/index.html >[Saad Tazi] Removal of unnecessary namespace declarations in XSLT: >unnecessary? Subjective, no? Examples? > No, for example, in configuration.en.html.xsl, for opencommerce, there is a unecessary namespace declaration : xmlns:performance="http://xmlns.fusion3.com/performance/1.0/" Not good because xmlns:performance="http://xmlns.fusion3.com/performance/1.0/" shows up everywhere in the resulting HTML. Also, when a declaration is indeed necessary, make sure it appears in the exlusion instruction along with "#default" (the default namespace) : xmlns:sku="http://xmlns.opencommerce.org/sku/1.0/" exclude-result-prefixes="#default sku" >[Saad Tazi] Removal tracing (System.out) from code: DONE for "my" code, >but do I have to remove all tracing (locales and jpg sizes from >Resources, in /org/opencommerce/iface/edi/javamail/Doc8xx classes...)? > Everything, except the init() tracing in the Resources class. >[Saad Tazi] Integrate namespace prefix declaration for dataisland xml, >in streamDocument methods: explanation please? > Use the startPrefixMapping and endPrefixMapping for namespace declaration and change the "qName" in all startElement and endElement methods so that sku --> sku:sku everywhere (you should see "sku:sku" when looking at the XML of a page). See : http://java.sun.com/j2se/1.4.2/docs/api/org/xml/sax/ContentHandler.html > >-----Original Message----- >From: dat...@li... >[mailto:dat...@li...] On Behalf Of >Vincent-Olivier Arsenault >Sent: September 10, 2003 3:59 PM >To: dat...@li... >Subject: [Dataisland-developer] TODO for the 1.0 release (scheduled on >October 1rst 2003) > >Hello! > >Here is my suggested TODO for the 1.0 release (scheduled on October 1rst > >2003). Please let me know what you think. > >Vincent-Olivier > > > >[Vincent-Olivier Arsenault] Home made serializer for XML (including >XHTML) and migrate serialization from HTML 4.01 to XHTML (inline >Javascript and Style escaping) in new package >org.dataisland.util.serialization, add render speed comment > >[Saad Tazi] New BUGS text with standard compliance, runtime, performance > >and algorithmic known issues text > >[Saad Tazi] New INSTALL text with infrastructure requirements and >installation procedures > >[Vincent-Olivier Arsenault] Clickable report & PO security > >[Vincent-Olivier Arsenault] New "relation" ontology that support >specification of compatible ontologies for each relation > >[Saad Tazi] All encodings to UTF-8 (files and file "encoding" attribute, > >if any) > >[Saad Tazi] Removal of unnecessary namespace declarations in XSLT > >[Vincent-Olivier Arsenault] Fix for cache invalidation bug > >[Vincent-Olivier Arsenault] Fix for OutOfMemoryError bug > >[Saad Tazi] Removal tracing (System.out) from code > >[Vincent-Olivier Arsenault] Improval data entry security > >[Vincent-Olivier Arsenault] Separattion of the code into four projects : > >Open Commerce, Buzzcut and SQL Store, Intelligenzia > >[Vincent-Olivier Arsenault] New coding standard documents for CSS, HTML, > >XML, SQL, XSLT, JavaScript and Java > >[Hugues Brunelle] Final logo > >[Vincent-Olivier Arsenault] Integration of Apache Maven : >http://maven.apache.org/ > >[Vincent-Olivier Arsenault] Removal duplicated code from Buzzcut, Open >Commerce, and Intelligenzia > >[Saad Tazi] Integrate namespace prefix declaration for dataisland xml, >in streamDocument methods > >[Saad Tazi] JavaDoc comments everywhere > >[Vincent-Olivier Arsenault] Database schema documentation for SQL Store, > >Buzzcut and OpenCommerce > >[Vincent-Olivier Arsenault] New architecture documentation > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Dataisland-developer mailing list >Dat...@li... >https://lists.sourceforge.net/lists/listinfo/dataisland-developer > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Dataisland-developer mailing list >Dat...@li... >https://lists.sourceforge.net/lists/listinfo/dataisland-developer > > |
From: Saad T. <st...@sy...> - 2003-09-11 14:45:00
|
Questions: [Saad Tazi] New BUGS text with standard compliance, runtime, performance and algorithmic known issues text: is it just a text file containing list of bugs? [Saad Tazi] New INSTALL text with infrastructure requirements and installation procedures: done in html. I just have to convert html to text, haven't I? [Saad Tazi] Removal of unnecessary namespace declarations in XSLT: unnecessary? Subjective, no? Examples? [Saad Tazi] Removal tracing (System.out) from code: DONE for "my" code, but do I have to remove all tracing (locales and jpg sizes from Resources, in /org/opencommerce/iface/edi/javamail/Doc8xx classes...)? [Saad Tazi] Integrate namespace prefix declaration for dataisland xml, in streamDocument methods: explanation please? -----Original Message----- From: dat...@li... [mailto:dat...@li...] On Behalf Of Vincent-Olivier Arsenault Sent: September 10, 2003 3:59 PM To: dat...@li... Subject: [Dataisland-developer] TODO for the 1.0 release (scheduled on October 1rst 2003) Hello! Here is my suggested TODO for the 1.0 release (scheduled on October 1rst 2003). Please let me know what you think. Vincent-Olivier [Vincent-Olivier Arsenault] Home made serializer for XML (including XHTML) and migrate serialization from HTML 4.01 to XHTML (inline Javascript and Style escaping) in new package org.dataisland.util.serialization, add render speed comment [Saad Tazi] New BUGS text with standard compliance, runtime, performance and algorithmic known issues text [Saad Tazi] New INSTALL text with infrastructure requirements and installation procedures [Vincent-Olivier Arsenault] Clickable report & PO security [Vincent-Olivier Arsenault] New "relation" ontology that support specification of compatible ontologies for each relation [Saad Tazi] All encodings to UTF-8 (files and file "encoding" attribute, if any) [Saad Tazi] Removal of unnecessary namespace declarations in XSLT [Vincent-Olivier Arsenault] Fix for cache invalidation bug [Vincent-Olivier Arsenault] Fix for OutOfMemoryError bug [Saad Tazi] Removal tracing (System.out) from code [Vincent-Olivier Arsenault] Improval data entry security [Vincent-Olivier Arsenault] Separattion of the code into four projects : Open Commerce, Buzzcut and SQL Store, Intelligenzia [Vincent-Olivier Arsenault] New coding standard documents for CSS, HTML, XML, SQL, XSLT, JavaScript and Java [Hugues Brunelle] Final logo [Vincent-Olivier Arsenault] Integration of Apache Maven : http://maven.apache.org/ [Vincent-Olivier Arsenault] Removal duplicated code from Buzzcut, Open Commerce, and Intelligenzia [Saad Tazi] Integrate namespace prefix declaration for dataisland xml, in streamDocument methods [Saad Tazi] JavaDoc comments everywhere [Vincent-Olivier Arsenault] Database schema documentation for SQL Store, Buzzcut and OpenCommerce [Vincent-Olivier Arsenault] New architecture documentation ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dataisland-developer mailing list Dat...@li... https://lists.sourceforge.net/lists/listinfo/dataisland-developer |
From: Vincent-Olivier A. <vi...@up...> - 2003-09-10 19:59:31
|
Hello! Here is my suggested TODO for the 1.0 release (scheduled on October 1rst 2003). Please let me know what you think. Vincent-Olivier [Vincent-Olivier Arsenault] Home made serializer for XML (including XHTML) and migrate serialization from HTML 4.01 to XHTML (inline Javascript and Style escaping) in new package org.dataisland.util.serialization, add render speed comment [Saad Tazi] New BUGS text with standard compliance, runtime, performance and algorithmic known issues text [Saad Tazi] New INSTALL text with infrastructure requirements and installation procedures [Vincent-Olivier Arsenault] Clickable report & PO security [Vincent-Olivier Arsenault] New "relation" ontology that support specification of compatible ontologies for each relation [Saad Tazi] All encodings to UTF-8 (files and file "encoding" attribute, if any) [Saad Tazi] Removal of unnecessary namespace declarations in XSLT [Vincent-Olivier Arsenault] Fix for cache invalidation bug [Vincent-Olivier Arsenault] Fix for OutOfMemoryError bug [Saad Tazi] Removal tracing (System.out) from code [Vincent-Olivier Arsenault] Improval data entry security [Vincent-Olivier Arsenault] Separattion of the code into four projects : Open Commerce, Buzzcut and SQL Store, Intelligenzia [Vincent-Olivier Arsenault] New coding standard documents for CSS, HTML, XML, SQL, XSLT, JavaScript and Java [Hugues Brunelle] Final logo [Vincent-Olivier Arsenault] Integration of Apache Maven : http://maven.apache.org/ [Vincent-Olivier Arsenault] Removal duplicated code from Buzzcut, Open Commerce, and Intelligenzia [Saad Tazi] Integrate namespace prefix declaration for dataisland xml, in streamDocument methods [Saad Tazi] JavaDoc comments everywhere [Vincent-Olivier Arsenault] Database schema documentation for SQL Store, Buzzcut and OpenCommerce [Vincent-Olivier Arsenault] New architecture documentation |
From: Vincent-Olivier A. <vi...@up...> - 2003-07-09 17:47:36
|
The OpenCommerce demo is live now! http://demo.opencommerce.dataisland.org/ This is going to be the demo we will use to fish clients and community members, make an ultra-emergency wishlist (mostly design, so Hugues and Sergei... it's all yours). Seeya! v-o |
From: Hugues B. <hu...@ec...> - 2003-07-03 02:48:16
|
Bonjour, Nous tenons =C3=A0 vous informez du changement suivant : =20 514 5218108 ne sera plus valide =C3=A0 partir du jeudi 3 juillet 18h00, = d=C3=A9sormais vous devrez signaler le 514 5211360 pour nous joindre. =20 Merci, =20 =20 Hugues & Niko |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-19 15:49:11
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body> Yet again, from the Oreilly Network, on creating PDFs dynamically.<br> <br> v-o<br> <br> <br> <a href="http://www.oreillynet.com/"><img src="cid:par...@up..." width="110" height="80" align="left" alt="O'Reilly Network" border="0"></a> <dummy> </dummy> <table border="0" cellspacing="0" width="468"> <tbody> <tr> <td><!-- dy --> <iframe src="http://ad.doubleclick.net/adi/onjava.ds/wsjart;pos=top_wsjart;sz=468x60;ord=1486759588?" width="468" height="60" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"> &lt;script&gt;&lt;/script&gt; </iframe> <noscript> <a href="http://ad.doubleclick.net/jump/onjava.ds/wsjart;abr=!ie;pos=top_wsjart;sz=468x60;ord=1486759588?"><img src="http://ad.doubleclick.net/ad/onjava.ds/wsjart;abr=!ie;kw=pos=top_wsjart;sz=468x60;ord=1486759588?" border="0" width="468" height="60" alt="Advertisement" /></a> </noscript> </td> </tr> </tbody> </table> <br clear="all"> <font face="verdana,arial,helvetica" size="1">Published on <b><a href="http://www.oreillynet.com/">The O'Reilly Network</a></b> (<a href="http://www.oreillynet.com/">http://www.oreillynet.com/</a>)<br> <a href="http://www.onjava.com/pub/a/onjava/2003/06/18/dynamic_files.html">http://www.oreillynet.com/pub/a/onjava/2003/06/18/dynamic_files.html</a><br> <a href="http://www.onjava.com/pub/a/general/print_code.html">See this</a> if you're having trouble printing code examples</font><br clear="all"> <!-- CS_PAGE_BREAK --> <h2> Dynamically Creating PDFs in a Web Application</h2> by <a href="http://www.onjava.com/pub/au/1230">Sean C. Sullivan</a><br> <!-- sidebar begins --><!-- don't move sidebars --><!-- sidebar ends --> 06/18/2003 <p>On a recent logistics project, a customer asked our team to build a web site that would allow users to query a legacy system for shipment information. The customer defined three main requirements:</p> <ol> <li>The shipping information had to be returned in the form of a PDF document.</li> <li>The PDF file must be downloadable through a web browser.</li> <li>The PDF file must be viewable using the Adobe Acrobat Reader.</li> </ol> <p>Our team had plenty of experience with J2EE web applications, but we had little experience with PDF documents. We needed to find a pure Java class library that could produce sophisticated PDF documents in a server-side web application. We found a solution that completely met our needs: <a href="http://www.lowagie.com/iText/">iText</a>.</p> <h3>iText Class Library</h3> <p>iText is an open source pure Java class library for creating and manipulating PDF documents. Bruno Low</p> <p>agie and Paulo Soares lead the project. The iText API enables a Java developer to programmatically create PDF documents. iText delivers a rich set of feature</p> <!-- sidebar ends --> <ul> <li>Support for both PDF and FDF documents</li> <li>Various page sizes</li> <li>Landscape or portrait layouts</li> <li>Margins</li> <li>Tables</li> <li>Hyphenation</li> <li>Page headers</li> <li>Page footers</li> <li>Page numbering</li> <li>Barcodes</li> </ul> <ul> <li>Fonts</li> <li>Colors</li> <li>Document encryption</li> <li>JPEG, GIF, PNG, and WMF images</li> <li>Ordered and unordered lists</li> <li>Shading</li> <li>Watermarks</li> <li>Document templates</li> </ul> <p>iText is an open source library. At the time of this writing, the iText software is available under a dual license: the Mozilla Public License (MPL) and the LGPL. Consult the iText web site for details. In this article, you'll see the iText API in action. We will demonstrate how to use iText and servlets to dynamically generate PDF documents in a server-side application.</p> <h3>Getting Started</h3> <p>First, you will need to obtain the iText JAR file. Visit the iText web site and download the current release. At the time of this writing, the current iText release is version 0.99. The iText web site provides API documentation and a comprehensive tutorial.</p> <p>In addition to iText, we'll be using servlets, too. If you aren't familiar with servlets, you can learn about them in Jason Hunter's book, <a href="http://www.oreilly.com/catalog/jservlet2/index.html?CMP=IL7015">Java Servlet Programming</a>. You will need to obtain a J2EE application server or a standalone servlet engine. Some good open source options are <a href="http://jakarta.apache.org/tomcat/">Tomcat</a>, <a href="http://jetty.mortbay.com/jetty/index.html">Jetty</a>, and <a href="http://www.jboss.org/">JBoss</a>. The rest of this article assumes that you are using Jakarta Tomcat 4.1.</p> <h3>The iText API</h3> <p>The iText API is intuitive and easy to use. Using iText, you will be able to programmatically create customized PDF documents. The iText library consists of the following packages:</p> <pre><code>com.lowagie.servlets com.lowagie.text com.lowagie.text.html com.lowagie.text.markup com.lowagie.text.pdf com.lowagie.text.pdf.codec com.lowagie.text.pdf.hyphenation com.lowagie.text.pdf.wmf com.lowagie.text.rtf com.lowagie.text.xml com.lowagie.tools</code></pre> <p>For generating PDF files, you'll need only <code>com.lowagie.text</code> and <code>com.lowagie.text.pdf</code>.</p> <p>Our example application uses these iText classes:</p> <pre><code>com.lowagie.text.pdf.PdfWriter com.lowagie.text.Document com.lowagie.text.HeaderFooter com.lowagie.text.Paragraph com.lowagie.text.Phrase com.lowagie.text.Table com.lowagie.text.Cell</code></pre> <p>The key classes are <code>Document</code> and <code>PdfWriter</code>. You will always use both of these classes when creating PDF documents. <code>Document</code> is an object-oriented representation of a PDF document. You can add content to the document by invoking methods provided by the <code>Document</code> class. A <code>PdfWriter</code> object associates a <code>Document</code> with a <code>java.io.OutputStream</code> object.</p> <!-- sidebar begins --> <table width="45%" border="0" cellspacing="12" cellpadding="6" align="right"> <tbody> <tr> <td valign="top" bgcolor="#efefef"> <h4>Coordinate System for iText Documents</h4> <p>When I wrote my first iText program, I stumbled over the coordinate system. I naively assumed that iText's coordinate system was identical to Swing's coordinate system. This is not the case.</p> <p>In Swing, the origin (0, 0) is located in the upper left-hand corner of a component. In iText, the origin is located in the bottom left-hand corner of a page.</p> </td> </tr> </tbody> </table> <!-- sidebar ends --> <h3>Using iText in a Web Application</h3> <p>During your design phase, you must decide how you plan to use iText. I've built web applications using both of the following techniques.</p> <h4>Technique A</h4> <p>Create the PDF file on the server's filesystem. The application uses <code>java.io.FileOutputStream</code> to write the file to the server's filesystem. The user will download the file via HTTP <code>GET</code>.</p> <h4>Technique B</h4> <p>Create the PDF file in memory using <code>java.io.ByteArrayOutputStream</code>. The application sends the PDF bytes to the client via the servlet's output stream.</p> <!-- sidebar begins --> <table width="220" border="0" cellspacing="12" cellpadding="6" align="right"> <tbody> <tr> <td valign="top" bgcolor="#efefef"> <p class="secondary"><b>Source Code</b></p> <p class="secondary">Download the source code for this example:<br> <a href="http://www.onjava.com/onjava/2003/06/18/examples/pdfservlet-files.zip">pdfservlet-files.zip</a></p> </td> </tr> </tbody> </table> <!-- sidebar ends --> <p>I prefer technique B to technique A because the application does not write to the server's filesystem, and the application is guaranteed to work in a clustered server environment. Technique A can fail if your application runs in a clustered environment, and the server cluster does not provide session affinity.</p> <h3>Example: PDFServlet</h3> <p>Our <a href="http://www.onjava.com/onjava/2003/06/18/examples/created-by-PDFServlet.pdf">example application</a> consists of a single class: <code>PDFServlet</code>. This servlet uses technique B from the previous section. The <code>OutputStream</code> is a <code>java.io.ByteArrayOutputStream</code>. With <code>ByteArrayOutputStream</code>, the PDF document bytes will be in memory. When <code>PDFServlet</code> receives an HTTP request, it will dynamically generate a PDF document and send the document to the client.</p> <p>The <code>PDFServlet</code> class extends <code>javax.servlet.http.HttpServlet</code> and imports two of the iText packages, <code>com.lowagie.text</code> and <code>com.lowagie.text.pdf</code>.</p> <h4>The <code>doGet</code> Method</h4> <p>Most servlets override either the <code>doPost</code> method or the <code>doGet</code> method. Our servlet is no different. The <code>PDFServlet</code> class overrides the <code>doGet</code> method. The servlet will generate a PDF file any time it receives an incoming HTTP <code>GET</code> request.</p> <p>In a nutshell, the servlet's <code>doGet</code> method does the following:</p> <ol> <li>Creates a <code>ByteArrayOutputStream</code> object that contains the PDF document bytes.</li> <li>Sets the HTTP response headers on the response object.</li> <li>Gets the servlet output stream.</li> <li>Writes the document bytes to the servlet output stream.</li> <li>Flushes the servlet output stream.</li> </ol> <p><img src="cid:par...@up..."><br> <em>Figure 1. Editing <code>doGet</code> in Eclipse</em></p> <h4>The <code>generatePDFDocumentBytes</code> Method</h4> <p>The <code>generatePDFDocumentBytes</code> method is responsible for creating the PDF document. The three most important objects in this method are the <code>Document</code> object, the <code>ByteArrayOutputStream</code> object, and the <code>PdfWriter</code> object. The <code>PdfWriter</code> associates the <code>Document</code> with the <code>ByteArrayOutputStream</code>.</p> <pre><code>Document doc = new Document(); ByteArrayOutputStream baosPDF = new ByteArrayOutputStream(); PdfWriter docWriter = null; docWriter = PdfWriter.getInstance(doc, baosPDF); // ... </code> </pre> <p>Adding content to a <code>Document</code> is done with the <code>add</code> method.</p> <pre><code>doc.add(new Paragraph( "This document was created by a class named: " + this.getClass().getName())); doc.add(new Paragraph( "This document was created on " + new java.util.Date())); </code> </pre> <p>When you are done adding content, close the <code>Document</code> and <code>PdfWriter</code> objects.</p> <pre><code>doc.close(); docWriter.close(); </code> </pre> <p>After closing the document, the <code>ByteArrayOutputStream</code> object is returned to the caller.</p> <pre><code>return baosPDF; </code> </pre> <p> The <code>ByteArrayOutputStream</code> contains all bytes for the PDF document.</p> <h4>HTTP Response Headers</h4> <p>In this application, we care only about four HTTP response headers: <code>Content-type</code>,<code>Content-disposition</code>,<code>Content-length</code>, and <code>Cache-control</code>. If you've never worked with HTTP headers before, consult the HTTP 1.1 specification.</p> <p>Examine the <code>doGet</code> method in the <code>PDFServlet</code>. You'll notice that the HTTP response headers are set before any data is written to the servlet output stream. This is an important, yet subtle, point.</p> <p>Let's look at each response header in more detail.</p> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tbody> <tr> <td> <p class="secondary"><!-- CS_PAGE_INDEX --> </p> <br> </td> <td> <p class="secondary" align="right"> <a href="http://www.onjava.com/lpt/a/%3C%21--CS_NEXT_REF--%3E"> </a></p> <br> </td> </tr> </tbody> </table> <!-- CS_PAGE_BREAK --> <p><!-- CS_PAGE_INDEX --> </p> <h4><code>Content-type</code></h4> <p>In servlets, <code>HttpServletResponse</code> has a content type that indicates the type of content that the response contains. For PDF files, the content type is <code>application/pdf</code>. If the servlet does not set a content type, the web browser may have a difficult time determining how to handle the file.</p> <p><code>PDFServlet</code> sets the content type with the following line: </p> <pre><code>resp.setContentType("application/pdf");</code></pre> <h4><code>Content-disposition</code></h4> <p>The <code>Content-disposition</code> header provides information that helps a web browser identify the content of the HTTP response. When a web browser reads this header, it can determine:</p> <ul> <li>That the HTTP response contains a file.</li> <li>The name of the file contained in the response.</li> <li>Whether the file should be displayed inside of the browser's main window or viewed by an external application.</li> </ul> <p>RFC 2183 provides a full explanation of the <code>Content-disposition</code> header.</p> <p>By setting the <code>Content-disposition</code> header appropriately, the servlet can instruct the browser to display the file "inline," or to treat it like an attachment.</p> <p><em>Example 1. Displaying a file inline</em></p> <pre><code>Content-disposition: inline; filename=foobar.pdf</code></pre> <p><em>Example 2. Attaching a file to the response</em></p> <pre><code>Content-disposition: attachment; filename=foobar.pdf</code></pre> <p>The following pseudo-code demonstrates how to set the header:</p> <pre><code>public void doGet(HttpServletRequest req, HttpServletResponse resp) { // ... resp.setHeader( "Content-disposition", "inline; filename=foobar.pdf" ); // ... }</code></pre> <h4><code>Cache-Control</code> Headers</h4> <p>Depending upon the nature of your application, you may or may not want web browsers to cache the PDF files that you are generating. There are a variety of HTTP headers that a server-side web application can use to control caching of content. Some examples are:</p> <ul> <li> <code>Cache-Control: no-cache</code> </li> <li> <code>Cache-Control: no-store</code> </li> <li> <code>Cache-Control: must-revalidate</code> </li> <li> <code>Cache-Control: max-age=30</code> </li> <li> <code>Pragma: no-cache</code> </li> <li> <code>Expires: 0</code> </li> </ul> <p>A full explanation of <code>Cache-Control</code> headers is found in the HTTP 1.1 specification.</p> <p>The <code>PDFServlet</code> sets <code>Cache-Control</code> to <code>max-age=30</code>. This header tells the web browser to cache the file for a maximum of 30 seconds.</p> <h4><code>Content-length</code></h4> <p>The <code>Content-length</code> header must be set to the number of bytes in the PDF file. If the <code>Content-length</code> header is not set correctly, the web browser may not be able to display the file. Example code might be:</p> <pre><code>ByteArrayOutputStream baos = getByteArrayOutputStream(); resp.setContentLength(baos.size());</code></pre> <h4>Sending the PDF Document to a Web Browser</h4> <p><code>PDFServlet</code> sends the PDF document to the client by writing bytes to the servlet's output stream. It obtains the output stream by calling <code>getOutputStream()</code> on the <code>HttpServletResponse</code> object. <code>getOutputStream</code> returns an object of type <code>javax.servlet.ServletOutputStream</code>.</p> <pre><code>ServletOutputStream sos; sos = resp.getOutputStream(); baos.writeTo(sos); sos.flush();</code></pre> <p>After writing all data to the stream, call the <code>flush()</code> method to send all bytes to the client.</p> <h4>Packaging and Deployment</h4> <p>To run the <code>PDFServlet</code> in Tomcat, you'll need to package the application in a WAR file. The iText JAR file (<i>itext-0.99.jar</i>) must be placed in the WAR file's <i>lib</i> directory. If you forget to include the iText JAR file, the servlet will fail with a <code>java.lang.NoClassDefFoundError</code>.</p> <h4>Running the Application</h4> <p>After the WAR file has been deployed, you are ready to test the servlet. Jakarta Tomcat listens for requests on port 8080.</p> <p>Point your web browser to <em> <a class="moz-txt-link-freetext" href="http://hostname:8080/pdfservlet/createpdf">http://hostname:8080/pdfservlet/createpdf</a></em>.</p> <p>When you visit the URL, the servlet executes and sends a PDF document back to your browser.</p> <h3>Beyond iText</h3> <p>iText provides a great low-level API for producing PDF documents. However, it may not be the best tool for every application.</p> <p>At my day job, we used iText in combination with Microsoft Word and Adobe Acrobat. First, our team designed a shipment form using Microsoft Word. Next, we converted the Word document to PDF using Adobe Acrobat. Then, using iText's template capability, we loaded the PDF file into our application. From there, it was quite easy to fill in data values on the form and output the final PDF document.</p> <p>For report-oriented web applications, tools like <a href="http://jasperreports.sourceforge.net/">JasperReports</a> provide a higher level of abstraction than iText.</p> <h3>Conclusion</h3> <p>When your Java application needs to dynamically create PDF documents, the iText class library is a great solution. You can experiment with iText's capabilities by enhancing and extending the code in this article. In a short time, you'll be able to impress your co-workers and customers with sophisticated PDF documents.</p> <h3>Additional Resources</h3> <ul> <li><a href="http://www.lowagie.com/iText/">http://www.lowagie.com/iText/</a></li> <li><a href="http://www.jpedal.org/">www.jpedal.org</a></li> <li> <a href="http://www.pdfbox.org/">www.pdfbox.org</a></li> <li><a href="http://xml.apache.org/fop/">xml.apache.org/fop</a></li> <li><a href="http://www.w3.org/Protocols/">HTTP 1.1 protocol specification</a></li> <li><a href="http://www.faqs.org/rfcs/rfc2183.html">RFC 2183</a></li> <li><a href="http://dmoz.org/Computers/Data_Formats/Document/Publishing/PDF/"> dmoz.org/Computers/Data_Formats/Document/Publishing/PDF</a></li> <li><a href="http://www.planetpdf.com/">www.planetpdf.com</a></li> <li><a href="http://www.pdfzone.com/">www.pdfzone.com</a></li> </ul> <p>If you are exploring Microsoft's .NET platform, be sure to check out <a href="http://sourceforge.net/projects/itextdotnet/">iTextdotNet</a> and <a href="http://sourceforge.net/projects/itextsharp/">iTextSharp</a>. Both projects are derived from the Java-based iText library. iTextSharp is written in Microsoft's C# language.</p> <p><i> <a href="http://www.onjava.com/pub/au/1230">Sean C. Sullivan</a> has been developing Internet applications with Java since 1996. His recent work includes B2B web applications, various open source projects and the development of an Internet e-commerce payment system at Intel. </i></p> <hr size="1" noshade="noshade"> <p>Return to <a href="http://www.onjava.com/">ONJava.com</a>.</p> <p><font face="verdana,arial,helvetica" size="1"><b>oreillynet.com</b> Copyright © 2003 O'Reilly & Associates, Inc.</font></p> </body> </html> |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-19 15:45:00
|
Hello, this is for my favourite designers in the world. There is a nice arti= cle=20 on the new CSS3 selectors on Oreilly Network. Here it is : http://www.xml.com/lpt/a/2003/06/18/css3-selectors.html *CSS 3 Selectors* *By* Russell Dyer Although the promise of Cascading Style Sheets (CSS) has been wondrou= s,=20 the progress has been wanting. As with all W3C <http://www.w3.org/>= =20 standards, there is the lengthy discussion process conducted by the= =20 related working group, then the problem of implementation by web brow= ser=20 vendors, and finally the unpredictable period of time for people to= =20 update to new versions of their browser. These steps can take a year = or=20 two each. To expedite the process, the CSS working group has started= =20 grouping related features into modules and releasing them separately,= =20 without waiting for completion of all modules. This allows browser= =20 vendors to proceed with implementation of CSS updates with the=20 confidence that standards won't be changed by the time the full relea= se=20 of CSS is approved. Ideally the result will be to reduce the process = by=20 a year or more. One CSS module that has recently been moved to /Recommended/ (or=20 finished) status by the CSS working group is the /Selectors/ module.= =20 Although it was completed just a few weeks ago, much of it has alread= y=20 been implemented by some of the browser vendors. The vendors seem ver= y=20 keen to expedite the /Selectors/ module since it can improve HTML and= =20 XML document design decidedly and for fairly little effort. As CSS= =20 grows, more selectors are adopted, although some can be pruned. This= =20 article will review all currently approved selectors. It will address= =20 the surviving CSS1 and CSS2 selectors in brief and the new CSS3=20 selectors in more detail. Basic Definitions A /cascading style sheet/ is used to set or change the styles of a= =20 markup document like a web page. Style sheets contain /rules/ that we= b=20 browsers follow when loading a web page, an XML document, or any=20 document written in a compatible markup language. A style sheet rule = is=20 composed of two basic components: a /selector/ and a /declaration/. T= he=20 selector is an identifier of a markup tag. For example, in HTML, p is= =20 the selector for <p> (or paragraph) tags. Declarations are the style= =20 settings that are to be applied by the browser when it encounters a= =20 match in a document for a selector. There are many different=20 declarations that may be made, but it is only selectors that concern = us=20 here. So when providing examples, I will focus on selectors and not= =20 comment on declarations. CSS1 Selector Basics The basic value of a selector is to point to objects or text for whic= h a=20 designer would like to set the style. For instance, suppose one decid= ed=20 to set to navy blue the main heading of each web page on a site=20 containing over a thousand pages. If all of the pages are linked to t= he=20 same style sheet and each page's main heading is wrapped in <h1> tags= ,=20 then the task would be simple and quick. It would be a matter of mere= ly=20 inserting into to the style sheet the simple rule below: h1{color: navy;} Occasionally designers need to select elements by /class/ or by uniqu= e=20 /identifiers/. Suppose a web page contains several tables and the= =20 designer wants the background color of some tables to be silver. Clas= s=20 selectors can be utilized by assigning a class to tables that are to = be=20 colored. One would place the first line below in the style sheet and= =20 start off silver tables in the document like the second line: table.special{background-color: silver;} <table class=3D'special'> To change the style for only one element on a site, an identification= =20 (ID) can be used: table#unique{background-color: pink;} <table ID=3D'unique'> In CSS1 a few /pseudo-class/ selectors were provided for anchor (<a>)= =20 elements: :link, :visited, :active,:hover, and :focus. These can be u= sed=20 to change the style of links depending on their state or on user=20 interaction. Two /pseudo-element/ selectors were also provided: the= =20 ::first-letter and the ::first-line selectors are for styling the fir= st=20 letter and the first line contained between selected tags.=20 Pseudo-elements are distinguished by two colons and they can affect= =20 partial content, but the declarations of pseudo-class selectors are= =20 applied to all of the content. A powerful function found in CSS1 is the /descendant combinator/. It= =20 allows the designer to select markup elements contained within anothe= r=20 specified element. One simply gives the parent element, then a space= =20 followed by the descendant. Don't confuse this syntax with that of= =20 grouping selectors (e.g., h1, h2, h3{...}). This rule will make the t= ext=20 within <quote> tags italic and green, but only when inside a paragrap= h: p quote{font-style: italic; color: green;} To style elements contained within elements that are contained within= =20 ancestor elements, that is, to style grandchildren elements, one woul= d=20 use an asterisk with spaces around it as a combinator: p * quote{font-style: italic; color: green;} From these basic selectors, designers have been able to standardize = the=20 styles of markup documents and reduce design and production time=20 significantly for the last few years. This has been especially critic= al=20 for XML developers since XML doesn't have default styling conventions= . CSS2 Selectors CSS2 offered a universal selector (*) to allow selection of specified= =20 elements of /all/ parents. For instance, this rule will select TD cel= ls=20 of all tables: *.td{font-size: 85%;} CSS2 expanded selectors to include discerning the values of element= =20 attributes. In HTML an image element (<img/>) may contain attributes= =20 like src, alt, align, and border. One can check if an image tag has a= =20 specified attribute. To set the padding only for images where the bor= der=20 is given, this rule will suffice: img[border]{margin: 5px;} You can also check if a value is contained in a space separated list= =20 contained in an attribute (e.g., img[alt~=3D"fish"]{...}). Or one can= =20 check the full value for an exact match: img[src=3D"logo.gif"]{border: 0;} CSS2 also expanded /descendant/ selector possibilities. The=20 pseudo-element selectors ::before and ::after allow one to add conten= t=20 before and after elements found. If one marked up the text of a play= =20 with XML tags around the dialog to identify a character's lines (e.g.= ,=20 <romeo>...</romeo>), one could use CSS to add text before and after e= ach=20 set of lines: romeo::before{content: "Romeo: \"";} romeo::after{content: "\"";} Starting in CSS2, designers can now change the style for the /first= =20 child/ of an element. To double the size of the first letter of the= =20 first paragraph of each section of a document (provided each section = is=20 enclosed in <div class=3D'section'></div> tags), try this: div.section:first-child::first-letter{font-size: 200%;} Notice that the parent is div; /section/ is the class, not the child.= =20 The child is whatever the browser finds first. It will double the siz= e=20 of the first letter of each child's content. A /child combinator/ selector was added to be able to style the conte= nt=20 of elements contained within other specified elements. For example,= =20 suppose one wants to set white as the color of hyperlinks inside of d= iv=20 tags for a certain class because they have a dark background. This ca= n=20 be accomplished by using a period to combine div with the class=20 /resources/ and a greater-than sign as a combinator to combine the pa= ir=20 with a, as shown below: div.resources > a{color: white;} Also added in CSS2 was the /direct adjacent combinator/. For example,= =20 imagine you want to indent all paragraphs in a document except for on= es=20 immediately following a sub-heading (<h2>). The second rule below sho= ws=20 an h2 selector combined with a p selector using a plus sign as the= =20 combinator to indicate that the declaration applies only if p=20 immediately follows h2: p{text-indent: 0.5in;} h2 + p{text-indent: 0;} Finally, consider the language selector. The :lang selector is for= =20 selecting a document of a specific language: html:lang(en){color: black;} xml:lang(en){color: gray;} Similarly, the hreflang attribute of the link element can be used wit= h=20 the attribute value selector that checks for a value and the same val= ue=20 followed by a hyphen. The following rule will match French (fr) and= =20 Belgian French (fr-be): link[hreflang|=3D"fr"]{font-style: italic; =09 by Russell Dyer Implemented CSS3 Selectors The Mozilla Project has already implemented several CSS3 selectors an= d=20 is working on implementing the rest soon. The other vendors aren't fa= r=20 behind, either. Let's look at what Mozilla has implemented first. Three more attribute selectors were added in CSS3; they allow for= =20 substring selection. One matches elements based on the beginning valu= es=20 of named attributes. This could be useful, for instance, if one wants= to=20 have different styles for hyperlinks to a sub-domain (e.g.,=20 sales.somesite.com), as opposed to the main domain (e.g., www.somesit= e.com): a[href^=3D'http://sales.']{color: teal;} To select elements based on the ending value of attributes, the carat= =20 above would be replaced with a dollar sign. The rule below would let= =20 users know that they are about to click on a link to a Java Server Pa= ge. a[href$=3D'.jsp']{color: purple;} CSS3 also provides substring matching irrespective of word boundaries= .=20 So if one wants to set the border for images from a particular direct= ory=20 (say, /images/artwork/), this rule will accomplish the task: img[src*=3D'artwork']{ border-color: #C3B087 #FFF #FFF #C3B087;} A few more pseudo-class selectors were added in CSS3. One is the :roo= t=20 selector, which allows designers to point to the root element of a= =20 document. In HTML, it would be <html>. Since :root is generic, it all= ows=20 a designer to select the root element of an XML document without=20 necessarily knowing it's name. To permit scrollbars when needed in a= =20 document, this rule would work: :root{overflow:auto;} As a complement to the :first-child selector, the :last-child was add= ed.=20 With it one can select the last element named of a parent element. Fo= r a=20 magazine site with articles contained in <div class=3D'article'></div= >=20 tags, where each has a last paragraph with author information, this r= ule=20 would change the font for each writer's blurb: div.article > p:last-child{font-style: italic;} The parent here is a div with /article/ as the class. Once the browse= r=20 finds such a div tag, it then looks for matching children (<p> tags= =20 here). It then selects the last paragraph and adjusts its style based= on=20 the rule's declaration. A new user interaction pseudo-class selector was added: the :target= =20 selector. To draw the user's attention to a span of text when the use= r=20 clicks on a same-page link, a rule like the first line below would wo= rk=20 nicely; the link would look like the second line, the highlighted spa= n=20 like the third: span.notice:target{font-size: 2em; font-style: bold;} <a href=3D'#section2'>Section 2</a> <p id=3D'section2'>...</p> To complement the direct adjacent combinator introduced in CSS2, the= =20 /indirect adjacent combinator/ was included in CSS3. It's used in= =20 situations where two specified elements are of the same parent and th= e=20 second element follows the first, but not immediately afterward. To= =20 render text as bold when it's contained within <tt> tags, but not whe= n=20 contained within a table, since there will be many elements for the= =20 browser to consider (e.g., <tr> and <td> tags) before it would reach = a=20 <tt> tag, a direct adjacent combinator selector wouldn't work. But an= =20 indirect adjacent combinator selector could handle this: tt{font-weight:bold;} table ~ tt{font-weight: normal;} Finally, a functional notation for selecting specified elements that= =20 fail a test has been created. The negation pseudo-class selector (:no= t)=20 can be coupled with almost any other selector that has been implement= ed.=20 To put a border around images that don't have a border specified, use= a=20 rule like this: img:not([border]){border: 1;} Unimplemented CSS3 Selectors The selectors that are yet to be implemented are a little more=20 complicated but very powerful; they should be implemented soon by the= =20 Mozilla Project. Almost all of them are pseudo-class selectors and ar= e=20 very similar. They will likely all be implemented by Mozilla simultan= eously. Quite often designers create online forms for users to complete. As t= he=20 user fills out portions of a form, based on the user's answers, some= =20 portions won't apply. To dynamically style text or input elements bas= ed=20 on whether an element is enabled or disabled, the :enabled and :disab= led=20 pseudo-class selectors have been devised: radio.creditcard_type:disabled{color: gray;} The :checked and :indeterminant pseudo-class selectors were created f= or=20 styling based on the status of check boxes and radio buttons. To=20 highlight the text associated with a check box once it has been check= ed,=20 use this rule: input:checked{background-color: blue; color: white;} For check boxes and radio buttons that start off with nothing checked= ,=20 one could highlight them to draw the user's attention to them as=20 required fields. In the example below, the input element has a class= =20 label of /required/: input.required:indeterminant{color: red;} Several descendant selectors await implementation. The :only-child= =20 selector is used to select elements that don't have any siblings. For= =20 instance, if one wants to indent paragraphs for sections (using XML= =20 <section> tags) only when there is more than one paragraph, this rule= =20 can solve the problem: section{text-indent: 0.5in;} section:only-child{text-indent: 0;} To style based on the uniqueness of type (i.e., no siblings), the= =20 :only-of-type selector is available. A related selector is :empty, us= ed=20 for selecting elements that have no children. Use the first rule belo= w=20 to style unique elements in a section and the second for sections wit= h=20 no children: section:only-of-type{text-style: italic;} section:empty{text-style: bold;} Along the same lines, one can style the first and last descendants ba= sed=20 on type. Suppose one has several documents (using <doc> tags) that= =20 involve the pattern of an introductory paragraph, several main=20 paragraphs, and a concluding paragraph. One could use this rule to st= yle=20 the first and last paragraphs differently: doc:first-of-type{text-style: bold;} doc:last-of-type{text-style: italic;} Keep in mind when using these pseudo-class selectors in which the= =20 element type is not specified, that stray elements might be styled= =20 unintentionally. A very handy and potentially confusing set of selectors that have bee= n=20 added in CSS3 are the /nth child/ pseudo-class selectors. These=20 structural selectors were made for designers to be able create precis= e=20 rules for climbing a document tree. Here's the basic format of an= =20 :nth-child selector: element:nth-child(an+b){...} The notation a represents the number of children by which the browser= is=20 to group. The notation b is the count of each grouping that is select= ed.=20 The n is always n and is not replaced with a number. To alternate the= =20 background of rows in a table, this rule could be deployed in the fut= ure: tr:nth-child(2n+1){background-color: magenta;} Notice here that the browser is to organize the rows into pairs and t= o=20 style the first of each pair. To highlight the first of three rows, t= hen=20 this is how the rule would read: tr:nth-child(3n+1){background-color: tan;} One could write a rule for each row of the three: tr:nth-child(3n+1){background-color: tan;} tr:nth-child(3n+2){background-color: fuschia;} tr:nth-child(3n+3){background-color: aqua;} There is some shorthand that can be used. Rather than 2n+1 for odd an= d=20 2n+2 for even, they can be replaced with odd and even: tr:nth-child(odd){background-color: maroon;} tr:nth-child(even){background-color: tan;} Incidentally, if a and b are equal, then b can be left out and the va= lue=20 of a will be the implied value of b. The rules below are equivalent a= nd=20 would be applied to the second row of each pair of rows (i.e., the ev= en=20 rows): tr:nth-child(2n+2){background-color: indigo;} tr:nth-child(2n){background-color: indigo;} For a non-repeating pattern, that is, to style one particular element= ,=20 then the a notation would be set to zero or just left out. The rules= =20 below are equivalent and will style just the eighth row: tr:nth-child(0n+8){background-color: silver;} tr:nth-child(n+8){background-color: silver;} tr:nth-child(8){background-color: silver;} To have the browser count elements starting from the bottom, use the= =20 :nth-last-child selector. The a notation uses a negative to indicate = a=20 reverse count. This rule styles the last two rows of a table: tr:nth-last-child(-n+2){background-color: violet;} To group on types for elements that are mixed with others, use=20 :nth-of-type selector. For instance, suppose one wants to alternate t= he=20 alignment of images in a document. These rules would do the trick: img:nth-of-type(2n+1){float: right;} img:nth-of-type(2n+2){float: left;} One can count based on type from the bottom, as well, by using the= =20 :nth-last-of-type selector. This rule aligns right only the last two = images: img:nth-last-of-type(-n+2){float: right;} CSS3 also has a content pseudo-class selector. The :contains selector= =20 searches the content of a specified element for a matching substring.= =20 This selector is for static media only (i.e., print and not screen= =20 display). A rule to style text when printed from a bullet list that= =20 contains the word "special," would look like this: li:contains("special"){text-style: italic;} Finally, to style text differently from the browser's default style t= hat=20 the user selects, the ::selection pseudo-element selector can be used= .=20 Typically, when text is selected by a user for copying, the backgroun= d=20 color changes to blue or black. This rule will alter the user selecte= d=20 text and limit alterations to text within paragraph tags: p::selection{ background-color: maroon; font-size: 200%;} Since this is a pseudo-element selector, only the selected text will = be=20 changed while selected and not the entire paragraph. Concluding Admissions Although I have attempted to cover all CSS selectors and give example= s=20 of each, there are some twists and aspects that I omitted. For instan= ce,=20 there are many ways to combine selectors to accomplish tasks. A few o= f=20 the example rules presented utilize two or more selectors, hinting at= =20 such potential complexities. I also didn't discuss the possibility of= =20 using different namespaces with selectors. There's also the issue of= =20 what to do about browsers that aren't CSS3 compatible, but are CSS2= =20 compatible. What will they ignore and with what will they meddle? If you would like more details, you can review the Web Consortium's= =20 documentation on Selectors=20 <http://www.w3.org/TR/2001/CR-css3-selectors-20011113/>. If you would= =20 like to test your browser for compatibility, try the Web Consortium's= =20 test pages <http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/>= .=20 For more on CSS in general, check out /CSS: The Definitive Guide=20 <http://www.oreilly.com/catalog/css/>/ by Eric Meyer. *XML.com* Copyright =A9 1998-2003 O'Reilly & Associates, Inc. |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-18 19:09:30
|
The module implementations are defined by their role in the checkout= =20 process : Billing information Module Shipping information Module Paiment Information Module Tax Module Shipping Module Order Processor Module Each module implementation is responsible for : 1. Getting it's directive from the checkout servlet entry in the web.= xml 1. Generating an interface for data capture or display, using the= =20 Data=EFsland form framework and the infoset xml 2. Specifying in which step each interface is supposed to appear in t= he=20 checkout process 2. Generating special items to the order (Taxes, Shipping fees, Servi= ce=20 fees, etc) 3. Acting on the checkout infoset, to complete the information, and= =20 making it's information available to other modules Each module is comprised of : 1. A Java class that overrides the=20 org.opencommerce.iface.dataisland.checkout.Module interface 2. A CSS class set 3. An XSLT template For one role, many module implementation should be available, at conf= ig=20 time, for example : Shipping Module : Canada Post UPS Order Processor : Email (with and without PGP, with or without database trace of the or= der) PaySystem Tax Module (See new E-U taxe regulation) : Canadian Business (QST, Provincial sales tax, HST) US Business Will be done by me : 1. All stub classes (Checkout.java, Module.java) 2. Adaptation of the current system to the new architecture v-o |
From: saad s. <s2...@sy...> - 2003-06-13 11:48:02
|
Hi, here is my list : - Wahid Lahlou : wah...@ho... - Patrick Coulombe : pa...@at... - François Cliche : cli...@ya... - AQIII (Association Quebecoise des Informaticiennes et Informaticiens Independants) : www.aqiii.org / aq...@aq... Fondée en 1993, cette association à but non lucratif regroupe des travailleurs autonomes du domaine de l'informatique. Elle leur offre une meilleure visibilité auprès des clients et différents services adaptés à leur situation. MISSION Augmenter la visibilité des travailleurs autonomes auprès d'un plus grand nombre de clients potentiels. Amener des informaticiennes et informaticiens pigistes à se rencontrer afin d'échanger sur des préoccupations communes. Bâtir un réseau facilitant les communications entre les membres et permettant de mieux s'entraider. Bye Saad ----- Original Message ----- From: "Vincent-Olivier Arsenault" <vi...@up...> To: <dat...@li...> Sent: Thursday, June 12, 2003 3:13 PM Subject: [Dataisland-developer] Reminder : Your guest list You KNOW what I mean.... Your guest list for the dataïsland-yul-1.0 meeting. Due tomorrow. ;-) v-o |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-12 22:07:22
|
/"Are telecom providers and ISPs going to continue to be necessary in the future? Why are we all paying subscriptions for communicating? What I want is a global extremely-high-speed ad-hoc wireless data & voice network, where the only entry cost is a mobile phone (or newtork card or whatever). Devices communicate peer to peer, or routed via other people's idle devices. Remember there is no subscriptions, so don't expect to piggy-back on someone's paid for DSL bandwidth. What are the technological barriers? What kind of protocols would you need? What hardware advances? How would you solve problems of geographic isolation? Are there theoretical, political or economic reasons it couldn't work?"/ http://ask.slashdot.org/askslashdot/03/06/12/1933247.shtml?tid=137&tid=193 |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-12 19:14:10
|
You KNOW what I mean.... Your guest list for the data=EFsland-yul-1.0 meeting. Due tomorrow. ;-) v-o |
From: Vincent-Olivier A. <vi...@up...> - 2003-06-11 23:18:43
|
http://slashdot.org/articles/03/06/11/039224.shtml?tid=103&tid=98&tid=99 mmm, not good. v-o |