Hi James, Thanks for the comments.
James Carlson ??: > Yong Sun writes: > >> I may not get your points, as my understanding, the documents (in SGML >> format, or html format, or any formats could be handled by Lucene) are >> parsed and processed in an off-line manner, which would not run on the >> server. >> > > What processes these files, and what assumptions does it make? > There are some scripts to parse the source SGML file and generate index files. Those SGML are from IPG(doc team) and G11n(localized documents) directly. Since this case is just for client app, I did not list them in the one pager. > Is this project related to "Sun i-Runbook" (maybe a replacement)? > No. > Is Lucene delivered in a way that others can use it? Should it be? > Lucene will not be use on server side. That means it will not be delivered to Opensolaris. > It seems to me that the NetBeans IDE (LSARC 2007/370) already delivers > Lucene. Why is another copy buried inside this project? Shouldn't > there be just one common delivery of that feature to the system? > > >> And then the indexes database is deployed on server (ideally >> would be opensolaris.org or opensolaris.com), and exports webservices >> interface for public access. >> > > Can users set up their own servers or is that a "Sun only" operation? > I would expect that to be a hard requirement for many customers, as > allowing direct Internet access from within a datacenter is still not > possible in many places. > It's a "Sun only" operation for setting up Web Server. You know the volumes for contents are big, it's impossible to put them into client app for off-line review. > >> Then the client utility (in java) accesses >> the webservices interface, to send user's queries and get the result. I >> think the architecture and the interactions between components are clear. >> > > Is it RMI or something else? Does it need to use specific TCP ports? > Does it coexist with other web services? Does the server > administrator have to do something to install or "deploy" the service? > > Client App simply use standard Web Service API which is provided by J2EE. No specific TCP ports, just http port (for SOAP) 80. > How does the user specify where he gets his information (which server > to use)? > The server info will be hard coded into the client app. > >> And the one pager is actually for integrating the client utility to >> opensolaris, while we described the whole picture to present more >> backgrounds, sorry that we did not make that clearly. >> > > That helps, but what case describes the rest of the project? Should > this case be dependent on (or at least reference) the rest of the > project? > > I still don't quite see how the proposed project is "obvious" enough > to be a fast-track. Why not run a full case for it? > Thanks for the suggestion, James. Can you help to be sponsor for this case? Or we can get somebody's help on this? Regards, Jeffrey
