[
https://issues.apache.org/jira/browse/STONEHENGE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704873#action_12704873
]
S.Uthaiyashankar commented on STONEHENGE-20:
--------------------------------------------
We can create a docs folder and put it inside there. I prefer a wiki, so that
we can generate pdf when doing release and include it (same way I have done to
.NET and PHP installation guide). But for the moment, we can put inside "docs"
folder.
By the way, shall we change *.mht to pdf or .html ? In linux, it is difficult
to open .mht file. You have to install some other extensions to get that
working. What about pdf?
> Documenting how to .NET, PHP and WSAS stacks to work together
> -------------------------------------------------------------
>
> Key: STONEHENGE-20
> URL: https://issues.apache.org/jira/browse/STONEHENGE-20
> Project: Stonehenge
> Issue Type: Task
> Components: Documentation
> Reporter: S.Uthaiyashankar
> Assignee: Ben Dewey
> Fix For: M1
>
> Attachments: Stonehenge Interop Grid_4-22-2009.xls, Stonehenge
> Interoperability Walkthru.doc, Stonehenge+Interoperability+Walkthru.doc,
> STONEHENGE-20.patch
>
>
> Have to document what are the configurations needed to get different stacks
> to work together. I suggest we document at least following scenarios
> dotnet-client -> php-bsl -> java-opssec/java-ops
> php-client->dotnet-bsl->java-opssec/java-ops
> php-client->java-bsl->dotnet-opssec/dotnet-ops
> dotnet-client->java-bsl->dotnet-opssec/dotnet-ops
> php-client->dotnet-bsl->php-opssec/php-ops
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
