|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
The services are in-place, https://github.com/keithwoodlock/mifosx/pull/71
A couple of points which might be of concern
Image fetch does not send the actual image but a base 64 encoded stream (which would mean the data sent is larger and more cpu cycles)
The reference Client would then create a Data URI for displaying the image (so image consumption on a pure _javascript_ client via ajax is easier)
I was not sure how I'd display the image is the image is returned "as is" using only JS. Will have another look at this after GK's demo