search

Unity3dAzure / AppServicesDemo

Azure App Services demos for Unity
https://www.deadlyfingers.net/tutorial/azure-app-services-for-unity3d
MIT License
27 stars 13 forks source link

Generalized naming of classes that aren't exclusive to Mobile Services #40

Closed krist00fer closed 6 years ago

krist00fer commented 7 years ago

I want to re-use the code in this library to call APIs implemented in Azure functions. The current Unity Code has a lot of references to Mobile Apps inside AppService even if the same implementation and classes can be used to call an API implemented in Azure Functions.

I propose that we try to evolve the AppService Unity Library to be more generic and to enable calling of Azure Functions.

This first pull request is targeting the "Demo Project" since I'd love your feedback on the changes I've done and it's more easy to discuss with a few demo scenes setup in Unity. Once we can come to an agreement I'm more than happy to submit the same changes to the other repository.

If you agree with me, then I see only a few more things that needs to be done in order to fully support my needs while calling Azure Function APIs like: Even more easy passing of parameters, calling Azure Functions that are "protected" by a code (can be worked around today by passing in the code in the name, but that could be done easier).

I'm very impressed with the work you've done so far

deadlyfingers commented 7 years ago

I'm thinking of moving to a new shared 'Azure for Unity' project... When I created the Blob Storage service for Unity there is a lot of code that can be shared between App Services and Storage Service projects. So is the best idea going forward to combine into one Azure for Unity library? That why we can have Azure App Service, Blob Service and Azure functions with one Azure shared lib that you can drop in to your Unity project.

deadlyfingers commented 6 years ago

Closing at this time as this will all be revised in the next release - the project will be refactored to use a shared RESTClient.