Some questions and comments...
The text under the bullet "Initiation of the synchronization request"
- I guess it's pasted from another document - refers to processing
files in the order specified in Step 1. I didn't see step 1 or an
equivalent list of file processing order.
In the communication transport layer section, there's a question
raised about putting the zipped returned files into the action
report. Why would we put it in the report? The already-existing
payload classes and interfaces - which the deploy command uses for
uploading archives to be deployed and which deploy and get-client-
stubs use for downloading client files - should work fine for this.
The returned files would go into the payload of the admin command's
HTTP response (in compressed form) but the report would remain as a
report. The logic already in the payload implementation would extract
the compressed files from the payload and store them in the right
places in the instance's directories.
The "Synchronization Issues/lib directory" talks about users adding
JARs to an app's lib directory updating the lib directory but
rewriting JARs not doing so. Are we saying that we would support
users operating directly on the lib directory in the DAS-owned
application directory: that is ${appsDir}/${appName}/lib? If so, it
seems arbitrary to limit it to just that directory. If, on the the
other hand, we're talking about a developer updating a JAR and
rebuilding the app and then redeploying, the redeployment logic would
touch the top-level app directory, right? So why would we need to
treat the lib directory specially? What have I missed?
I may have more later.
- Tim
On Mar 16, 2010, at 10:00 PM, Bill Shannon wrote:
> I've updated my design spec at
> http://wiki.glassfish.java.net/Wiki.jsp?page=V3.1Clustering
> I've added more information about asadmin commands, and expanded
> a few other sections. As usual, send me any comments.
>
> (I sure wish we had change bars for this wiki...)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>