Dealing with Json or XML isn't really a problem, but basically what
i'm facing is another deal : those guys chain custom action (for
example, login/logincheck/loginok/homeView...), these actions filling
a different task. So, applying this to our current problem (user enter
bargain code, submits,
yes basically instead of a jsp-generated htmla json or xml text should do
the job
and those guys don't even have to worry about how to present the
information. all they need to do is pass the data or tell you that the
handshake was unsuccessful
thanks a lot.
They have also been talking about servlets, and again, that's not my
world; should I encourage this pratice ? will it ease the job between
us
well I think you have to decide a working model by between you and your java
guys.As you know and probably what your trying to do, you make almost make
the browser work like client-server model (not that they are not, just not
so clearly i guess).
If you want do all the display and UI logic by
Well the 2 major ways to communicate between server and client are XML and
JSON I guess, besides HTML of course.I believe any hardcore java developer
is familiar with XML. So if you are willing to deal with XML you can ask
them to format their input(for you, or output for them) in decided XML
5 matches
Mail list logo
