Hey Don,
I'm on the team with Ed so I can answer some of your questions.
Basically what we're trying to do is store the model data (information
underlying some custom layers and other abstract data) and run the GUI on
the client machine. What we mean by "thick client" is that the client
uses the JVM rather than a simple jpg/etc website in the style of google
earth.
Yes, we're trying to do something that is probably fairly standard.
However, the way we were trying to do it (shipping across the full
MapHandler via RMI) produced EOFException's as noted in the previous
e-mail.
We were trying to keep the RMI cut through the application minimal, which
is why we did it at such a high level. If it's necessary to dig into the
Layer level, then so be it, but it'd be nice if we could keep this as high
as possible.
Thanks,
Daniel.
> Hi Ed,
>
> I don't think you'd want the MapHandler to have references to objects
> on the server side, I'd keep it focused on the client side
> components. I'd only allow the Layers to have RMI connections to the
> server, either to get OMGraphics from the server or information it
> needs to create OMGraphics on the client side. You can have the
> layer either push updated information back to the server, or let the
> shared OMGraphic objects do it.
>
> How are you launching and configuring the client? I'm confused by
> your question about the 'thick client' approach - it seems like a
> standard OpenMap application that has layers that talk to servers for
> their information. Just like an applet, but with OpenMap running as
> an application instead (outside of the applet sandbox).
>
> - Don
>
> On Jun 26, 2006, at 3:08 PM, Ed MacKerrow wrote:
>
>> Dear OM Users Group,
>>
>> We are migrating an OM app from standalone to run on a server. We
>> would like to follow the MVC pattern with the model on the server,
>> and a thick client for the view. We are having trouble
>> transferring the MapHandler instance over RMI to the client. We
>> get a EOF exception. This could be that the MapHandler has too
>> many references to other objects on the server side and timeout issue?
>>
>>
>> We need a better way to design things.
>>
>> Our requirements include:
>>
>> 1) client side viewing and editing of model data
>> 2) updating of OMGraphics on the server as the model/simulation
>> evolves
>> 3) we would like a Swing UI on the client side instead of web
>> page. (we could try using Ajax, but we are more comfortable with
>> Swing).
>>
>> Has anyone out there attempted this “thick client” approach? Any
>> suggestions and guidance is greatly appreciated.
>>
>> Thank you,
>>
>> Ed
>> --
>> =================================================================> Ed
>> MacKerrow
>> T-13, Complex Systems Group, Theoretical Division, Los Alamos
>> National Laboratory
>> Mail Stop B-213, Los Alamos, New Mexico 87545
>> (505) 665-3491 (office), (505) 690-0549 (cell), (505)665-3003 (fax)
>> JWICS: lomacep_at_lanlitp.ic.gov SEAS: lomacep_at_doe.ic.gov
>
>
--
Daniel Summerhays,
Los Alamos National Laboratory,
Theoretical Division, T-13,
MS B213
Los Alamos, NM, 87545
(505)665-0123
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Tue Jun 27 2006 - 14:05:22 EDT